document: .i18nrc is conf file, not .babelrc #10
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Extracting msgids fails if no .i18nrc file is provided
|
Wouldn't it be better to try to solve the real issue? Either by using good defaults for the entries in the |
|
I agree and created #11 for this. |
jfschwarz
suggested changes
Mar 3, 2017
README.md
Outdated
| } | ||
| ``` | ||
|
|
||
| Create the file `.i18nrc` and add a configuration object for gettext message extraction: | ||
|
|
||
| ```json |
There was a problem hiding this comment.
It should without the "extra" and "gettext" wrapping
jfschwarz
approved these changes
Mar 3, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Extracting msgids fails if no .i18nrc file is provided.
I re-ordered the setup items, because it seems that the .i18nrc file location depends on the path provided to
i18n-extract(which I don't fully understand).