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
sprinkles uses .yml as the extension for the project file. many other systems use .yaml (which is recommended by the yaml maintaines see. It is probably easier to check for both extension, rather than change the documentation to stress that the file must be .yml (not .yaml).
The text was updated successfully, but these errors were encountered:
To me personally, it's a non-issue, but if you want to make the change yourself (shouldn't be difficult at all), feel free to send patches.
Note however that once I get around to rewriting the CLI structure, which will probably introduce breaking changes anyway, I will probably make it such that you have to pass the project filename explicitly, which makes the naming issue a matter of convention rather than technical implementation (i.e., you can pick whatever filename you want, extension and all).
it is a non-issue for me as well - just clash between two program by different authors which use different conventions. I assume your solution will be more flexible and I can live with the current solution (but I might do a patch, if i have to look into this part of the code). at the moment i work through the docs.
sprinkles uses .yml as the extension for the project file. many other systems use .yaml (which is recommended by the yaml maintaines see. It is probably easier to check for both extension, rather than change the documentation to stress that the file must be .yml (not .yaml).
The text was updated successfully, but these errors were encountered: