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
{{ message }}
This repository has been archived by the owner on Jan 19, 2018. It is now read-only.
I believe there should indeed be an easy way to add information for other programs, e. g. in a form of extensions, mentioned in the spec. For example making it a requirement in the spec that parsing mustn't be strict should prevent a lot of problems with extensibility in the future IMO.
Speaking from the point of DevAssistant, we are very open to taking as much metadata from the Atomicfile as possible - this makes the maintenance easier for the upstream developer. However, we would appreciate having the possibility to have some bits of information in the Atomicfile too. A concrete example of what we may need is a freeform field in the Atomicfile where we can link DevAssistant-specific files (those are stored elsewhere in the tree), and maybe add some other information not useful to other consumers of the Atomicfile.
How much do we need to define for specific providers and extensions? Are these defined externally to the spec or does it need to be consolidated here?
The text was updated successfully, but these errors were encountered: