Adding extra fields to the default schema

[ineo7]

its safe to adding extra fields to the default schema ? and the validated in the core config of the library ?
in the features any updated to the library can brake it ?

CREATE TABLE IF NOT EXISTS users (
  id BIGSERIAL,
  email VARCHAR(255) NOT NULL,
  password VARCHAR(255),
  username VARCHAR(255) NOT NULL, // HERE EXTREA username FIELD ?
  email_verified_at TIMESTAMPTZ,
  created_at TIMESTAMPTZ NOT NULL DEFAULT CURRENT_TIMESTAMP,
  updated_at TIMESTAMPTZ NOT NULL,
  PRIMARY KEY (id)
);
CREATE UNIQUE INDEX idx_users_email ON users (email);

func validateUserFields(ctx *limen.AdditionalFieldsContext) (map[string]any, error) {
	if ctx.GetBody() == nil {
		return nil, nil
	}
	if ctx.IsEmpty("username") {
		return nil, limen.NewLimenError("first_name is required", http.StatusBadRequest, nil)
	}
	return map[string]any{
		"username": ctx.GetBodyValue("username"),
	}, nil
}

    Schema: limen.NewDefaultSchemaConfig(
	    limen.WithSchemaUser(
		    limen.WithUserAdditionalFields(validateUserFields),
	    ),
    ),

[thecodearcher]

Yes, adding extra columns to users and persisting them with WithUserAdditionalFields is supported and safe.

Your callback is the right place to validate input. Return an error (e.g. limen.NewLimenError(...)) to reject bad data; returned map keys must match your DB column names.

A few notes:

• The column must already exist in your DB (migration/CLI/manual ALTER TABLE).
• Check ctx.GetBody() == nil — the callback can run outside HTTP requests.
• Always validate/sanitize client input before returning it.
• Your example error says "first_name is required" but checks "username".
• Default schema includes first_name/last_name unless you use WithUserIncludeNameFields(false).

Future Limen updates shouldn't break custom columns as they are additive.

If you're adding username with credential-password, use built-in username support instead:

credentialpassword.WithUsernameSupport(true),
credentialpassword.WithRequireUsernameOnSignUp(true),

Use WithUserAdditionalFields for custom fields the plugins don't handle.

Docs: Schema