-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add most recently added fields as top-level exports #3078
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
Add most recently added fields as top-level exports #3078
Conversation
3ceb829
to
2328072
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.
Thanks! LGTM.
Should this be code generated?
It should, ideally. But there is a mix of manual and generated classes in the import list, so the file cannot be fully generated. I'll see if I can add a unit test that ensures that all the generated fields can be imported, which should be easier to do. |
8f244c4
to
dd9588e
Compare
* Add most recently added fields as top-level exports * add unit test to ensure all fields are exported (cherry picked from commit 9c61068)
* Add most recently added fields as top-level exports * add unit test to ensure all fields are exported (cherry picked from commit 9c61068)
* Add most recently added fields as top-level exports * add unit test to ensure all fields are exported (cherry picked from commit 9c61068)
Indirect discovery while working on #3075 is that the most recent batch of
Field
subclasses were not included as top-level exports. This PR adds them.