Skip to content

fix: Naming conflicts when properties are named "field" or "define" #793

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 2 commits into from
Aug 12, 2023

Conversation

dbanty
Copy link
Collaborator

@dbanty dbanty commented Aug 12, 2023

Closes #781

@codecov
Copy link

codecov bot commented Aug 12, 2023

Codecov Report

Merging #793 (0701b94) into main (4f9a3c1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #793   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           49        49           
  Lines         1971      1971           
=========================================
  Hits          1971      1971           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@dbanty dbanty merged commit 7e3676d into main Aug 12, 2023
@dbanty dbanty deleted the 781-fix-field-naming-error branch August 12, 2023 18:52
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.

Since d28bc12 we generate broken code if there is a field called field
1 participant