Skip to content

Nested-objects-encoding #4

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

Merged
merged 1 commit into from
Jan 29, 2025
Merged

Conversation

joshuat
Copy link
Member

@joshuat joshuat commented Jan 29, 2025

Carries over changes from parse-community#8209 to fix encoding of nested objects, specifically dates.

Carries over changes from parse-community#8209 to fix encoding of nested objects, specifically dates.
Copy link

@richardharrington richardharrington left a comment

Choose a reason for hiding this comment

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

lol this seems like a pretty major oversight for them not to have taken care of in the first place.

Ideally we'd merge this into the 4.3.0-hustle-9.1 branch as well, but these branches are kind of a shit show and we've sort of abandoned the idea of adding to that branch -- which is not working for obscure reasons -- until we get off parse server (or until we have three months till the Mongo upgrade and we haven't made any progress on Parsectomy and we start panicking again).

I was planning to do a short timebox for some possible quick fixes to 4.3.0-hustle-9.1 anyway, so I'll make sure to cherry-pick this over if I do. Or rebase it on 4.3.0-hustle-8, or whatever.

@joshuat joshuat merged commit f9960b5 into 4.3.0-hustle8 Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants