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

Prefer to use .state in staticCommands #1078

Merged
merged 14 commits into from
Aug 9, 2021
Merged

Conversation

exyi
Copy link
Member

@exyi exyi commented Jul 24, 2021

This should fix the annoying synchronization issues when state is updated
in user code and staticCommand is invoked, which reads the old data :/

This should fix the annoying synchronization issues when state is updated
in user code and staticCommand is invoked, which reads the old data :/
exyi added 2 commits July 26, 2021 13:15
This is a hack, we should track which objects flow where, but it's easier to put a bunch of ko.unwraps where...
@exyi exyi marked this pull request as ready for review July 30, 2021 12:34
exyi and others added 7 commits July 30, 2021 13:06
A null Type was slipping into the ViewModelInfoAnnotation which
lead to the SerializationMap being null. This null case is now handed.

ExtensionParameter translation now has handling for the case when the
parameter has null ParameterType, so less nulls should slip into
the VM Info annotation
@quigamdev quigamdev merged commit 2dfd623 into main Aug 9, 2021
@quigamdev quigamdev deleted the staticCommand-useState branch August 9, 2021 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants