v0.0.2-alpha.26

Released all 12 packages at 0.0.2-alpha.26 in lockstep (nextly, create-nextly-app, and 10 @nextlyhq/* packages).

What's changed

@nextlyhq/adapter-drizzle

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

@nextlyhq/adapter-mysql

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

• Updated dependencies [6964718]:

  • @nextlyhq/adapter-drizzle@0.0.2-alpha.26

@nextlyhq/adapter-postgres

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

• Updated dependencies [6964718]:

  • @nextlyhq/adapter-drizzle@0.0.2-alpha.26

@nextlyhq/adapter-sqlite

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

• Updated dependencies [6964718]:

  • @nextlyhq/adapter-drizzle@0.0.2-alpha.26

@nextlyhq/admin

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

• Updated dependencies [6964718]:

  • @nextlyhq/ui@0.0.2-alpha.26

create-nextly-app

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

nextly

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

• Updated dependencies [6964718]:

  • @nextlyhq/adapter-drizzle@0.0.2-alpha.26
  • @nextlyhq/adapter-mysql@0.0.2-alpha.26
  • @nextlyhq/adapter-postgres@0.0.2-alpha.26
  • @nextlyhq/adapter-sqlite@0.0.2-alpha.26

@nextlyhq/plugin-form-builder

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

• Updated dependencies [6964718]:

  • @nextlyhq/admin@0.0.2-alpha.26
  • nextly@0.0.2-alpha.26
  • @nextlyhq/ui@0.0.2-alpha.26

@nextlyhq/storage-s3

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

@nextlyhq/storage-uploadthing

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

@nextlyhq/storage-vercel-blob

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.

@nextlyhq/ui

Patch Changes

• #123 6964718 Thanks @aqib-rx! - Single edit forms no longer ask for a title and slug. A Single is a one-instance document whose identity is fixed by its config (label + slug), but the admin previously rendered title and slug as editable, required inputs — forcing redundant input for values already determined by the definition.

  The single edit form now shows the title (from the single's label) and slug (from the configured slug) as read-only, non-editable fields, and submitting never errors on them. EntrySystemHeader and EntryMetaStrip gain opt-in lockIdentity/lockSlug flags (default off, so collection entry forms are unchanged); for singles the title/slug are seeded from config, the client validation for those two fields is relaxed, and slug auto-generation is disabled.