-
Notifications
You must be signed in to change notification settings - Fork 3
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
1840: Properly serialize activity log and fix it #1844
base: main
Are you sure you want to change the base?
Conversation
The additional |
1eca958
to
6928fde
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General note: This should be deployed as a hotfix. so please do not merge anything from main
One small improvement. Rest looks good to me! 👍
Thx for the quick fix
Tested on chrome.
Also tested card creation for koblenz, nuernberg and bayern (also bulks)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on Brave and Firefox. At nuernberg
It works great 👌
Interesting use of reduce
at serializeCard/deserializeCard .
- Unrelated point: BavariaCardTypeExtension is weird TBH are we inserting a component within an object?
Yes, kind of. We set a component as object property. In the end, a component is just a render function that returns a react element in any case. That way, we can have generic components for each extension (without needing to know anything about the actual implementation/look). |
Short description
The activity log was broken for a while due to serializing not happening properly. This introduces proper typing and serializing.
Proposed changes
fromSerialized
andserialize
methods to each extension and for cardsSide effects
Testing
See issue.
Resolved issues
Fixes: #1840