Describe the bug
The Attachments aspect in @cap-js/attachments is annotated with a misspelled Capabilities term. In db/index.cds the aspect declares:
annotate Attachments with @Capabilities.UpdateRestrictions.NonUpdateableProperties : [ content ];
The property is spelled NonUpdat**ee**ableProperties, but the OData Capabilities vocabulary (Capabilities.UpdateRestrictionsType) only defines NonUpdat**a**bleProperties. Because the term is unknown, the CDS compiler ignores the annotation and emits a warning for every entity that flattens the aspect. Two consequences:
A compiler warning is raised at each projection of the aspect.
The intended restriction is silently lost — content is not actually marked as non-updatable, even though the annotation clearly intends it to be.
Compiler warning (one per exposed *_attachments entity):
[WARNING] db/schema.cds:242:3: “NonUpdateableProperties” is not a known property for
“@Capabilities.UpdateRestrictions” of type “Capabilities.UpdateRestrictionsType”
(in entity:“…_attachments”/“@Capabilities.UpdateRestrictions”)
To Reproduce
Steps to reproduce the behavior:
Add @cap-js/attachments (v3.12.1, also confirmed in latest v3.13.1) to a CAP project.
Use the Attachments aspect on an entity, e.g. attachments : Composition of many Attachments;.
Expose the entity through a service.
Run cds build (or cds compile).
Observe the “NonUpdateableProperties” is not a known property … warning for each exposed attachments entity.
Environment:
@cap-js/attachments: 3.12.1 (typo also present in 3.13.1, the current latest)
@sap/cds: 9.9.1 / @sap/cds-dk: 9.9.0
Expected behavior
The aspect should use the correct vocabulary term so that no warning is raised and content is actually marked as non-updatable:
annotate Attachments with @Capabilities.UpdateRestrictions.NonUpdatableProperties : [ content ];
[ ] is it a regression issue?
No — the misspelled term is present across all released versions up to and including the current latest (3.13.1).
Screenshots
Not applicable (compiler/CLI output included above).
Describe the bug
The Attachments aspect in
@cap-js/attachmentsis annotated with a misspelled Capabilities term. Indb/index.cdsthe aspect declares:annotate
Attachmentswith@Capabilities.UpdateRestrictions.NonUpdateableProperties : [ content ];The property is spelled
NonUpdat**ee**ableProperties, but the OData Capabilities vocabulary (Capabilities.UpdateRestrictionsType) only definesNonUpdat**a**bleProperties. Because the term is unknown, the CDS compiler ignores the annotation and emits a warning for every entity that flattens the aspect. Two consequences:A compiler warning is raised at each projection of the aspect.
The intended restriction is silently lost —
contentis not actually marked as non-updatable, even though the annotation clearly intends it to be.Compiler warning (one per exposed
*_attachmentsentity):Steps to reproduce the behavior:
Add
@cap-js/attachments(v3.12.1, also confirmed in latest v3.13.1) to a CAP project.Use the Attachments aspect on an entity, e.g.
attachments : Composition of many Attachments;.Expose the entity through a service.
Run
cds build(orcds compile).Observe the
“NonUpdateableProperties”is not a known property … warning for each exposed attachments entity.Environment:
@cap-js/attachments: 3.12.1 (typo also present in 3.13.1, the current latest)
@sap/cds: 9.9.1 / @sap/cds-dk: 9.9.0
Expected behavior
The aspect should use the correct vocabulary term so that no warning is raised and content is actually marked as non-updatable:
annotate Attachments with @Capabilities.UpdateRestrictions.NonUpdatableProperties : [ content ];[ ] is it a regression issue?
No — the misspelled term is present across all released versions up to and including the current latest (3.13.1).
Screenshots
Not applicable (compiler/CLI output included above).