Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for jstransformers, deprecate Transformers #1928

Merged
merged 1 commit into from
May 18, 2015

Conversation

ForbesLindesay
Copy link
Member

So many people have done such fantastic work to make this possible. This will make it really easy to independently publish/update/fix each separate filter.

// these marker transformers haven't made sense in a long time
css: 'verbatim',
js: 'verbatim',
};

Choose a reason for hiding this comment

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

Might be able to use the transform.inputFormats values for these alternatives.

Copy link
Member Author

Choose a reason for hiding this comment

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

We could, but I think in this case it's probably better to get people to specify the exact canonical name of that transform. It prevents any potential ambiguity and makes loading the relevant transformer much simpler (otherwise we have to look for all possible transformers in the parent path and load all of them just in case one of them matches).

ForbesLindesay added a commit that referenced this pull request May 18, 2015
Add support for jstransformers, deprecate Transformers
@ForbesLindesay ForbesLindesay merged commit 2d65331 into master May 18, 2015
@ForbesLindesay ForbesLindesay deleted the jstransformers branch May 18, 2015 14:42
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