On Thu, Jun 25, 2015 at 4:18 PM, Stefan Seifert <[email protected]> wrote: > currently a sling provisioning file [1] has just a file extension "txt". This > is ok for all current usecases, but makes it difficult for tooling to apply a > file validation or syntax highlighting. > > we are currently working on some configuration generation tooling that uses > validators to ensure the generated files are valid. we can detect sling > provision file format only by extension and loading the content and doing > some heuristics on it (e.g. "contains '[feature '"). quite ugly. > > it would make sense to invent a new file extension specific to sling > provisioning files, e.g. ".provisioning". > > WDYT?
Well, it is just a text file, so txt sounds right. It also means that a text editor is always associated with it in desktop environments + IDEs, which is a plus. Would adding a some metadata to the file in the form of comments work? Robert
