This PR adds necessary changes that make the switch from .yaml to .yml possible with elegance! Though the effect of the change is straightforward, I still wanted to highlight the main behavioral changes to give you a chance to review.
elAPI will only recognize elapi.yml as its configuration file name in all three search locations (/etc, $HOME/.config, .).
For commands like bill-teams and get, if YAML is passed to --format/-F to define the export data format, the exported data will have .yml extension.
$ elapi bill-teams info -F yml --export
^^^
# or
$ elapi bill-teams info -F yaml --export
^^^^
# In both cases, data will be exported to "datetime_bill_teams.yml" file to maintain the .yml convention.
^^^
However, if a full file path is given, then the file name provided will be honored.
$ elapi bill-teams info --export ~/bill_teams_info.yaml
^^^^
Exports to "bill_teams_info.yaml" file (".yaml" remains unchanged).
In GitLab by @mhxion on Nov 29, 2023, 23:06
Merges change-YAML-config-extension-name -> main
This PR adds necessary changes that make the switch from
.yaml
to.yml
possible with elegance! Though the effect of the change is straightforward, I still wanted to highlight the main behavioral changes to give you a chance to review.elapi.yml
as its configuration file name in all three search locations (/etc
,$HOME/.config
,.
).bill-teams
andget
, if YAML is passed to--format
/-F
to define the export data format, the exported data will have.yml
extension.Exports to "bill_teams_info.yaml" file (".yaml" remains unchanged).