v0.0.2-alpha.4

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

What's changed

@nextlyhq/adapter-drizzle

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

@nextlyhq/adapter-mysql

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

• Updated dependencies [af98b55]:

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

@nextlyhq/adapter-postgres

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

• Updated dependencies [af98b55]:

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

@nextlyhq/adapter-sqlite

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

• Updated dependencies [af98b55]:

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

@nextlyhq/admin

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

• Updated dependencies [af98b55]:

  • @nextlyhq/ui@0.0.2-alpha.4

create-nextly-app

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

nextly

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

• Updated dependencies [af98b55]:

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

@nextlyhq/plugin-form-builder

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

• Updated dependencies [af98b55]:

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

@nextlyhq/storage-s3

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

@nextlyhq/storage-uploadthing

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

@nextlyhq/storage-vercel-blob

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.

@nextlyhq/ui

Patch Changes

• #23 af98b55 Thanks @mobeenabdullah! - Fix Single document fields appearing empty after a component-field rename. Schema-apply and external-schema-update handlers invalidated ["collections"], ["entries"], ["singles"], and ["components"] — but Single document data lives under a separate ["single-documents"] namespace (used by useSingleDocument), which was never invalidated. After a rename, useSingleSchema refetched with the new field name while useSingleDocument kept serving cached data keyed by the old name, so the form rendered data[newName] as undefined and the field appeared blank until a hard refresh. Collections were unaffected because useEntry lives under ["entries"], which was already in the invalidation list. The ["single-documents"] key is now invalidated alongside the others. Also propagate the Draft/Published status flag through buildFullDesiredSchema for both collections and singles, mirroring the earlier preview-pipeline fix so the full-schema build path doesn't drop the column either.