Export LinkifyIt instance to allow customisation #28
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
ivanalejandro0
added a commit
to SpiderOak/react-linkify
that referenced
this pull request
Oct 14, 2016
|
👍 |
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.
This is a simple change that allows users to leverage
linkifyfeatures that are not accessible right now. In particular, adding and removing schemas.This change brings flexibility to the component and adds almost no complexity. Users can reuse their knowledge of the
linkifylibrary.I think it is a better idea to give access to the
linkifyinstance and "automagically" support any change or new feature that they do instead of passing through options as stated on #20, that IMHO, will overcomplicate the component.