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

Meteor.settings on client replaces < with &lt; entity #3730

Closed
wackazong opened this Issue Feb 14, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@wackazong

wackazong commented Feb 14, 2015

When I use a string in Meteor settings which contains the < character, on the client the character is replaced with the < entity. It does not happen on the server side.

Tested: Mac 10.10.1 with Chrome, FF and Safari latest. I cannot see in the documentation that this would be by design.

Terminal transcript:

$ git clone https://github.com/wackazong/meteor-settings-entities-bug
Cloning into 'meteor-settings-entities-bug'...
remote: Counting objects: 16, done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 16 (delta 1), reused 11 (delta 0)
Unpacking objects: 100% (16/16), done.
Checking connectivity... done.
$ cd meteor-settings-entities-bug/
$ meteor --settings settings.json 
[[[[[ ~/Development/meteor-settings-entities-bug ]]]]]

=> Started proxy.                             
=> Started MongoDB.                           
=> Started your app.                          

=> App running at: http://localhost:3000/
I20150214-22:28:42.439(1)? <p>text</p>

glasser added a commit that referenced this issue Feb 18, 2015

glasser added a commit that referenced this issue Feb 18, 2015

glasser added a commit that referenced this issue Feb 18, 2015

glasser added a commit that referenced this issue Feb 18, 2015

@glasser glasser closed this in d4d349c Feb 18, 2015

@glasser

This comment has been minimized.

Member

glasser commented Feb 18, 2015

Thanks, fixed.

glasser added a commit that referenced this issue Feb 18, 2015

Fix tests from #3730 fix
Whoops, accidentally only ran webapp tests before pushing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment