Use JSON instead of "PHP-style nested object syntax" to send actual data types in the metadata
See original GitHub issueCurrently, because bugsnag-js
serializes metadata as “PHP-style nested objects” into the query string, the actual data types get lost.
Preserving the data types in the reports is important to debug certain type-related issues which are not uncommon in weakly typed JavaScript.
The data types could be preserved by using JSON.
The public Bugsnag API is advertised to take JSON payload: https://docs.bugsnag.com/api/error-reporting/#json-payload
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:17 (4 by maintainers)
Top Results From Across the Web
JSON nested objects - IBM
JSON nested objects. Objects can be nested inside other objects. Each nested object must have a unique access path. The same field name...
Read more >Nested JsonObject in object for dynamic data when serializing?
I have the following response object that I want to serialize to send in the body of all my HTTP responses:
Read more >Example: TD_JSONSHRED Nested Objects and Dot Notation ...
This example creates a small JSON document with nested objects, inserts it into a database table as a CLOB data type, then uses...
Read more >Tutorial: Querying nested data with Amazon Redshift Spectrum
Amazon Redshift Spectrum supports querying nested data in Parquet, ORC, JSON, and Ion file formats. Redshift Spectrum accesses the data using external ...
Read more >JSON | Data Types - GeeksforGeeks
JSON supports mainly 6 data types: string; number; boolean; null; object; array. Note: string, number, boolean, null are simple data types or ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There’s a lot of good points and interesting discussion in here. It makes sense that we give more thought to supporting a more modern delivery mechanism in addition to the existing options, though the library’s API for handling this would need to be refined somewhat. I posted some related ideas on @jacobmarshall’s related issue here. The next steps are to explore and define this idea more concretely, hopefully to have an expressive yet performant (and backwards compatible) library.
@sompylasar That’s a great point too. Thanks!