Minor Changes
-
Add
sitecore-tools project experimental listto show the experimental features available in the current Content SDK app. (e1d0156)
The command reads the app's framework package (@sitecore-content-sdk/nextjsor@sitecore-content-sdk/angular) and prints each feature with its enabled status. Framework packages now exportexperimentalFeaturesCatalogfrom their/experimentalentry. -
minor
@sitecore-content-sdk/contentdependency update:-
[angular] Metadata, Open Graph and Schema.org & JSON-LD Support
-
@sitecore-content-sdk/content:resolvePageMetadataFields(withPageMetadataRouteFields/ResolvedPageMetadataFields) moved from@sitecore-content-sdk/nextjsto@sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules.@sitecore-content-sdk/nextjskeeps re-exportingPageMetadataRouteFields. -
@sitecore-content-sdk/angular: addedPageMetadataService+<sc-page-meta-tags [route]>(<title>, metadata and Open Graph<meta>tags via Angular'sTitle/Metaservices) andJsonLdSchemaService+<sc-json-ld-schema [page]>(a single<script type="application/ld+json">in<head>, normal mode only). Re-exported thePageMetadataFields,MetadataFields,OpenGraphFields,OpenGraphImageField(Value)andPageMetadataRouteFieldstypes. -
Angular template:
LayoutComponentrenders both components;RouteFieldsextendsPageMetadataFields. (c7801c3)- Avoid throwing errors in scClient calls when context ID in browser is missing.
- Replaces the GraphQL client used by scClient with no-op fallback in browser context, when public content ID is missing, preventing
getPage(),getDictionary()and other GraphQL-bound method from throwing. - Adds a guard into
getHeadLinks()call to return empty results when client context ID is missing, instead of throwing an error. - Client Context ID becomes required for rendering head links. (5184ea7)
-