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

Remove special chars from JSON message to make widget more robust #3

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

xpix
Copy link

@xpix xpix commented Nov 17, 2016

No description provided.

@chilipeppr
Copy link
Owner

Hi Frank,

I'm not comfortable putting that change in there. I think this is the kind
of code that creates issues in the future when somebody is actually trying
to send these characters and nobody can figure out why they aren't getting
through. The only thing I would feel comfortable with is looking for
something that would only detect from TinyG and only fix TinyG, but nothing
broader.

The other problem here fundamentally is TinyG shouldn't be sending a bad
character, so I'd much rather solve this by getting Alden to update the
firmware so no weird characters are being sent.

-John

On Thu, Nov 17, 2016 at 6:30 AM, Frank Herrmann [email protected]
wrote:


You can view, comment on, or merge this pull request online at:

#3
Commit Summary

  • remove special characters from JSON text
  • Made some changes to ChiliPeppr widget using Cloud9
  • remove all special ASCII Chars
  • Made some changes to ChiliPeppr widget using Cloud9

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHidbc2C7w5V-Aq2WInd4uq0zL0qx5dDks5q_GTygaJpZM4K1Xxx
.

@xpix
Copy link
Author

xpix commented Nov 17, 2016

Ok, no problem. I can also add a console message if found we not allowed characters in JSON.

But yes, we should inform alden.

Am 17.11.2016 um 17:19 schrieb John Lauer [email protected]:

Hi Frank,

I'm not comfortable putting that change in there. I think this is the kind
of code that creates issues in the future when somebody is actually trying
to send these characters and nobody can figure out why they aren't getting
through. The only thing I would feel comfortable with is looking for
something that would only detect from TinyG and only fix TinyG, but nothing
broader.

The other problem here fundamentally is TinyG shouldn't be sending a bad
character, so I'd much rather solve this by getting Alden to update the
firmware so no weird characters are being sent.

-John

On Thu, Nov 17, 2016 at 6:30 AM, Frank Herrmann [email protected]
wrote:


You can view, comment on, or merge this pull request online at:

#3
Commit Summary

  • remove special characters from JSON text
  • Made some changes to ChiliPeppr widget using Cloud9
  • remove all special ASCII Chars
  • Made some changes to ChiliPeppr widget using Cloud9

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHidbc2C7w5V-Aq2WInd4uq0zL0qx5dDks5q_GTygaJpZM4K1Xxx
.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

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