-
Notifications
You must be signed in to change notification settings - Fork 300
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 commandline option for passing features to cargo expand during codegen #2284
Conversation
Hi! Thanks for opening this pull request! 😄 |
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.
(just a quick one-line nit when skimming it)
Looks like there is a 10k line of code diff, possibly because some cargokit folders etc are missing. One quick way to fix this error is to revert unwanted changes in those folders. Feel free to ping me if you need any suggestions to make CI pass etc, or ping me when it is ready for review! |
Yes, I just realized that happened when running |
69328d2
to
c73f805
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2284 +/- ##
==========================================
- Coverage 98.98% 98.96% -0.02%
==========================================
Files 489 489
Lines 20231 20252 +21
==========================================
+ Hits 20025 20042 +17
- Misses 206 210 +4 ☔ View full report in Codecov by Sentry. |
The code LGTM, maybe we can add a test for it. For example, maybe we can
|
f418c86
to
319e2f7
Compare
While I have these tests added, I am trying to find a way to make linting/clippy respect the correct feature flags in a clean way. Will let you know when its fully working again |
1e26146
to
038620e
Compare
038620e
to
e3373e2
Compare
Appears to be fully working again with the tests |
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.
Great job! Mainly some nits :)
Do these latest changes work so far? |
Looks great! I will review again within a day. Btw next time when you are ready, feel free to use "request a review" button or tell me. |
Oh yes sorry will use that next time |
It's OK! |
c7b0a53
to
4f4acc0
Compare
The progress looks good, and feel free to ping me when the things above are handled! |
4f4acc0
to
b77625c
Compare
seems to be ready |
Great! I will review probably within a day |
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.
Great! Ready to merge after nits
2bc411e
to
26f152b
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.
Great! I am ready to merge and only one missing nit (other two can be fixed by using github's button)
@all-contributors please add @fmeef for code |
I've put up a pull request to add @fmeef! 🎉 |
a466ffa
to
16f57c4
Compare
16f57c4
to
1aa537e
Compare
1aa537e
to
518c0ba
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.
Fixed
Hi! Congrats on merging your first pull request! 🎉 |
This fixes #2283