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.

Sign up for GitHub

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

Jump to bottom

if we want to rely on json encodeability for data objects, we should have an optional convert param for LogMessageCallback #10

Closed
devoncarew opened this issue Sep 27, 2018 · 1 comment
Closed

if we want to rely on json encodeability for data objects, we should have an optional convert param for LogMessageCallback #10

devoncarew opened this issue Sep 27, 2018 · 1 comment

Comments

@devoncarew
Copy link
Contributor

If we want to rely on json encodeability for data objects, we should have an optional convert param for LogMessageCallback (the same as what dart:convert's encodeJson takes) - jsonEncode(Object object, { Object toEncodable(Object nonEncodable) }).
@pq pq mentioned this issue Sep 30, 2018
Open
@devoncarew
Copy link
Contributor Author

I think this is covered by the new data logging?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@devoncarew