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

Investigate Json overflow mechanism via Toth.Json #387

Closed
kMutagene opened this issue Jun 19, 2024 · 1 comment · Fixed by #455
Closed

Investigate Json overflow mechanism via Toth.Json #387

kMutagene opened this issue Jun 19, 2024 · 1 comment · Fixed by #455
Assignees

Comments

@kMutagene
Copy link
Member

See https://learn.microsoft.com/en-us/dotnet/standard/serialization/system-text-json/handle-overflow on System.Text.Json

In short, this can be used as a preliminary implementation to unblock #365 from #384/#385 . Untyped fields could target a specific field that is present on all datamodel types to dump the tokenized json there. After #385 is implemented, it is still useful work because the Dynamic object would just replace that field, but access to the tokenized json is still necessary to implement that.

@github-actions github-actions bot added the Status: Needs Triage This item is up for investigation. label Jun 19, 2024
@kMutagene kMutagene assigned kMutagene and HLWeil and unassigned kMutagene Jun 19, 2024
@Freymaurer Freymaurer added Type: Feature Request This item is confirmed by the maintainers to be a request for a new feature Status: Needs Triage This item is up for investigation. and removed Status: Needs Triage This item is up for investigation. Type: Feature Request This item is confirmed by the maintainers to be a request for a new feature labels Jun 21, 2024
@HLWeil HLWeil moved this to Ready in ARCStack Jun 27, 2024
@HLWeil HLWeil removed the Status: Needs Triage This item is up for investigation. label Jun 27, 2024
@kMutagene
Copy link
Member Author

@HLWeil could you shortly summarize your progress on this here so we can close this and focus efforts on #384 ? IIRC you solved this in a private repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants