-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
Allowed the generated values
statement to optionally be static. Fixes #415
#435
Conversation
Codecov Report
@@ Coverage Diff @@
## main #435 +/- ##
=======================================
Coverage 98.26% 98.26%
=======================================
Files 20 20
Lines 691 691
=======================================
Hits 679 679
Misses 12 12
|
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.
Could we add a unit test for the fix? Even though the coverage hasn't been changed, it actually did.
The fix is already covered in existing unit tests. Both So I do believe it is tested (both with and without static), so I would be unsure what test to add. |
Appreciate your explanation! |
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.
LGTM. I'm not so familiar with versioning so I guess we can add CHANGELOG entries later.
What does this change?
Allowed the generated values statement to optionally be static. For flat listings, each asset is
static
but thevalues
property is not, making it inaccessible. Now when generating flat listings, values is static like all the other assets.Fixes #415 🎯
Type of change
Please delete options that are not relevant.
Checklist:
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
melos run unit:test
)melos run format
to automatically apply formatting)