feat!: generated file naming syntax #135
Open
+262
−37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current implementation applies the flags
--filename
differently and has different naming conventions for generated files depending on the commandThis PR introduces another breaking change requested by clients which solves the situation by establishing a common format for generated files:
Where:
<filename>
is the name of the file. Customizable by the user with the--filename
flag<suffix>
is an optional suffix to differentiate the files. By default is going to be thespaceId
and is customizable by the user with the--suffix
flag<extension>
is the file extension. By default isjson
(Not configurable)Example:
Will generate the languages in the following path
.storyblok/languages/my-languages.dev.json
If you would like to use a timestamp as the suffix you can use:
storyblok pull-languages --space=12345 --filename=my-languages --suffix="$(date +%s)"
Warning
The
--filename
will be ignored in the case that--separate-files
is used on the commands that supports it.