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
Currently we have config file with default name: config
Each file, in contrast with folder have extension. And extension show as what content this file have.
Why config file by default do not have extension?
We have some issue with default name, for example if we have config file with default name, we cannot create directory with name config. I think if we will add extension for default config file name, it's will resolve this issue.
Next one, our config file have a custom format. We use tab character as space. If we insert space character, gostatic cannot parse this file. Maybe we can use TOML format or YAML format for our config file?
What do you think?
We can add new format for our config file, for example YAML, it can resolve issue with TAB characters in config file, and added extension for config file. We can use this format and filename as default, and use current format and filename as option, not to break compatibility.
The text was updated successfully, but these errors were encountered:
I really don't want to switch to YAML, which is a one of the worst human-readable syntaxes. Also, current name and format is modeled after Makefile (see, no extension).
In other words, current situation is not accidental, it's how I want it to be. :)
Currently we have config file with default name: config
Each file, in contrast with folder have extension. And extension show as what content this file have.
Why config file by default do not have extension?
We have some issue with default name, for example if we have config file with default name, we cannot create directory with name config. I think if we will add extension for default config file name, it's will resolve this issue.
Next one, our config file have a custom format. We use tab character as space. If we insert space character, gostatic cannot parse this file. Maybe we can use TOML format or YAML format for our config file?
What do you think?
We can add new format for our config file, for example YAML, it can resolve issue with TAB characters in config file, and added extension for config file. We can use this format and filename as default, and use current format and filename as option, not to break compatibility.
The text was updated successfully, but these errors were encountered: