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

Don't update properties with update: "no" #1536

Merged
merged 2 commits into from Jan 3, 2023
Merged

Don't update properties with update: "no" #1536

merged 2 commits into from Jan 3, 2023

Conversation

exyi
Copy link
Member

@exyi exyi commented Dec 20, 2022

Properties not tranferred server->client shouldn't be updated after a
postback. Doing this lead to unnecesary reverts of client-side
changed value and broke ClientToServerInPostbackPath bind direction.

Resolves #1534

client-side, we don't use deserialize in the first request, so it's
pointless to distinguish the two cases
Properties not tranferred server->client shouldn't be updated after a
postback. Doing this lead to unnecesary reverts of client-side
changed value and broke ClientToServerInPostbackPath bind direction.

Resolves #1534
@exyi exyi added this to the Version 4.1 milestone Jan 3, 2023
@exyi exyi merged commit e7cc5c8 into main Jan 3, 2023
@exyi exyi deleted the fix/transfer-in-path branch January 3, 2023 15:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Strange behaviour with bind attribute Direction.ClientToServerInPostbackPath
2 participants