Skip to content

Conversation

@miyanokomiya
Copy link
Contributor

#52

I am not confident in English well, please check it.

Copy link
Member

@TheAlexLichter TheAlexLichter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd be nice to have a "working" example in the docs as well

README.md Outdated
```

### Use custom extractors
Each extention can be applied just one exractor.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Each extention can be applied just one exractor.
Only one extractor can be applied to each file extention.

README.md Outdated

### Use custom extractors
Each extention can be applied just one exractor.
If you apply a custom extractor to the extentions applied default extractor already, you have to override the default value.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you apply a custom extractor to the extentions applied default extractor already, you have to override the default value.
If you want to apply a custom extractor to the extensions that the default extractor already covers, you have to override the default extractor. This is only possible with the functional notation.

README.md Outdated
extensions: ['html', 'vue', 'js']
},
{
extractor: CustomVueExtractor, // This cannot work, because above extractor is applied to 'vue' already.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
extractor: CustomVueExtractor, // This cannot work, because above extractor is applied to 'vue' already.
extractor: CustomVueExtractor, // This will not work, because the above extractor is applied to 'vue' already.

Copy link
Member

@TheAlexLichter TheAlexLichter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd be nice to have a "working" example in the docs as well

@miyanokomiya miyanokomiya force-pushed the note_for_custom_extractors branch from c3cf432 to d6b6f33 Compare August 10, 2019 00:13
@miyanokomiya
Copy link
Contributor Author

@manniL
Thanks for your checking. I fixed messages and replace a example with working one.

@TheAlexLichter TheAlexLichter self-assigned this Aug 10, 2019
@TheAlexLichter TheAlexLichter self-requested a review August 10, 2019 18:43
@TheAlexLichter TheAlexLichter merged commit 7ad9c8e into Developmint:master Sep 5, 2019
@miyanokomiya miyanokomiya deleted the note_for_custom_extractors branch September 6, 2019 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants