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

Make mhchem have a config parameter to select the new version #1537

Merged
merged 1 commit into from
Aug 5, 2016

Conversation

dpvc
Copy link
Member

@dpvc dpvc commented Jun 24, 2016

Make mhchem have a config parameter that can be used to select the new version (when it is available on the CDN) or the old legacy version. The default is the legacy version, so this is an opt-in for the new mhchem, which is what I think we agreed on. The parameter is named legacy, but I am open to other suggestions.

I had to put the old version inside an if-then statement, but I didn't re-indent it, as I didn't want the difference to look extensive than it is. Volker may want me to change that. :-)

…w version (when it is available on the CDN) or the old legacy version.
@pkra pkra added this to the MathJax v2.x.x milestone Jun 24, 2016
@pkra
Copy link
Contributor

pkra commented Jun 24, 2016

The parameter is named legacy, but I am open to other suggestions.

OK with me but I also don't have strong feelings about it.

@dpvc dpvc changed the title Make mhchem have a config parameter that can be used to select the ne… Make mhchem have a config parameter to select the new version Jul 5, 2016
@zorkow
Copy link
Member

zorkow commented Jul 23, 2016

I think this is for @pkra as he is been in the mhchem loop.

@pkra
Copy link
Contributor

pkra commented Aug 5, 2016

Sorry I missed my mention.

LGTM

@dpvc dpvc merged commit 199badf into mathjax:develop Aug 5, 2016
@dpvc dpvc deleted the mhchem-opt-in branch August 5, 2016 15:21
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.

3 participants