Mixed data and meta
See original GitHub issueIt seems that json-api-normalizer
can’t work if I have an entity with type meta
. Am I right?
Why not use entities
and result
top-level keys, like original normalizr
does?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Mixed Data Meta-analysis: Integration of Individual Participant ...
Meta -analysis synthesizes quantitative information from multiple sources by reconciling differences in order to produce empirical evidence ...
Read more >Individual participant data meta-analysis with mixed ... - PubMed
One-stage meta-analysis of individual participant data (IPD) poses several statistical and computational challenges.
Read more >Mixed metadata architecture with a shared repository = Data ...
Figure 5 shows such a mixed approach where a shared repository for managing globally rele- vant metadata is introduced, but only connected to...
Read more >Individual participant data meta-analysis with mixed-effects ...
IPD meta-analysis with mixed-effects models. Combining data of individuals from different studies, which investigate different populations and ...
Read more >Mix and match analytics: data, metadata, and machine ...
Mix and match analytics: data, metadata, and machine learning for the win. Creating winning analytics solutions means combining and making ...
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
I think, it’s possible to fix this behavior without a breaking change using an extra option.
normalize(json, { buildResult: true })
// { entities: {}, result: {} }We can even log a warning message that
normalize(json)
andnormalize(json, { endpoint })
are deprecated ways of usage of the library.I can send a PR.
Thoughts?
Thanks. We’re moving from HAL to JSON:API. It sounds to be more flexible and easier for me as frontend dev to ask the data. Plus I don’t need to create any schema, it’s already done by json:api convention/son-api-normalizer. Loving it!