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

arbitrary objects #55

Merged
merged 1 commit into from
Apr 4, 2018
Merged

arbitrary objects #55

merged 1 commit into from
Apr 4, 2018

Conversation

dbfannin
Copy link
Owner

@dbfannin dbfannin commented Apr 2, 2018

Allow arbitrary objects to be logged to console (this will allow circular objects to be parsed), but not to HTTP Service

@dbfannin dbfannin mentioned this pull request Apr 2, 2018
JSON.stringify(next)
}

return next;
Copy link
Contributor

Choose a reason for hiding this comment

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

Won't this actually cause a schema change for the output of the information logged to the server? If I remember correctly, the message that is created from this parser is always a string, which might cause problems for anyone trying to use it.

Copy link
Owner Author

Choose a reason for hiding this comment

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

This doesn't change the message (which is correct that it is always a string). The additional is an any[], so I think we'll be fine there. I think we want to keep the type of the logged additional, but still verify it is valid.

@dbfannin dbfannin merged commit 36196c1 into master Apr 4, 2018
@dbfannin dbfannin deleted the feature/fixObjectParsing branch April 4, 2018 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