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

Fix IsDirty generator when using a custom namespace #267

Merged
merged 1 commit into from
Mar 22, 2023
Merged

Conversation

kzu
Copy link
Member

@kzu kzu commented Mar 22, 2023

In this case, the generator shouldn't emit anything at all, since the legacy generation will be in place, which already emits the right IsDirty boolean property.

@kzu kzu added the bug label Mar 22, 2023
@kzu kzu enabled auto-merge (rebase) March 22, 2023 17:46
In this case, the generator shouldn't emit anything at all, since the legacy generation will be in place, which already emits the right IsDirty boolean property.
@kzu kzu force-pushed the dev/FixIsDirtyLegacy branch from ffc261f to 48c7db4 Compare March 22, 2023 17:49
@kzu kzu merged commit 5031f81 into main Mar 22, 2023
@kzu kzu deleted the dev/FixIsDirtyLegacy branch March 22, 2023 17:51
@devlooped devlooped locked and limited conversation to collaborators Sep 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant