You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an enum[] is in a config, sometimes it is parsed by the metadata extractor as a element[].
From my understanding this happens when the enum type is declared outside of the file where the config is declared.
We are regularly seeing blueprint developers coming to us with this error in the metadata file that is resulting in an error when importing the blueprint in the CMS.
It would be nice to have either:
a fix to support this use case
the extractor to fail the build when the detected type is incompatible with the default value of the property
For sure a fix would be ideal but detecting the use case and failing the build would already be very good for the blueprint developers to detect and fix this issue quickly.
Current result
{
"description": "The document types of the preferred method",
"category": "functionalities",
"label": "preferred Documents",
"name": "preferredDocuments",
"type": "element[]",
"reference": {
"library": "@refx/kiosk-common",
"name": "KioskDocumentType"
},
"values": [
"BoardingPass"
]
}
Expected result
{
"description": "The document types of the preferred method",
"category": "functionalities",
"label": "preferred Documents",
"name": "preferredDocuments",
"type": "enum[]",
"choices": [
"BoardingPass"
],
"values": [
"BoardingPass"
]
}
Additional comments
No response
The text was updated successfully, but these errors were encountered:
Package name
extractors
Package version
latest
Reproduction steps
Hello,
When an enum[] is in a config, sometimes it is parsed by the metadata extractor as a element[].
From my understanding this happens when the enum type is declared outside of the file where the config is declared.
We are regularly seeing blueprint developers coming to us with this error in the metadata file that is resulting in an error when importing the blueprint in the CMS.
It would be nice to have either:
For sure a fix would be ideal but detecting the use case and failing the build would already be very good for the blueprint developers to detect and fix this issue quickly.
Current result
Expected result
Additional comments
No response
The text was updated successfully, but these errors were encountered: