[X] I searched open requests and couldn't find a duplicate
What is the idea?
The keyword list for the Information Property List (Info.plist) files is very limited.
This can be done in one of two ways:
Add all keywords to the schema. This allows for type validation, but is not scalable as the list needs to be kept up-to-date with Apple. Additionally, many keywords may not be relevant for menuinst, so adding all keywords may not be worth the effort.
Add a free-form item to the schema (e.g., info_plist). This is scales well and invalid keywords do not break the app, according to my tests. However, type validation is not possible with this approach. This could be solved if a standard was published somewhere, but I'm not aware of any such document.
Why is this needed?
The current list of keywords for Info.plist is limited and new keywords require an updated schema (and possibly CEP) to be published. See, e.g., https://github.com/conda/menuinst/pull/194 for how adding new keywords currently needs to be performed.
What should happen?
The schema should be expanded to allow for any valid Info.plist keyword for MacOS apps.
Checklist
What is the idea?
The keyword list for the Information Property List (
Info.plist) files is very limited.This can be done in one of two ways:
menuinst, so adding all keywords may not be worth the effort.info_plist). This is scales well and invalid keywords do not break the app, according to my tests. However, type validation is not possible with this approach. This could be solved if a standard was published somewhere, but I'm not aware of any such document.Why is this needed?
The current list of keywords for
Info.plistis limited and new keywords require an updated schema (and possibly CEP) to be published. See, e.g., https://github.com/conda/menuinst/pull/194 for how adding new keywords currently needs to be performed.What should happen?
The schema should be expanded to allow for any valid
Info.plistkeyword for MacOS apps.Additional Context
No response