-
Notifications
You must be signed in to change notification settings - Fork 137
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
Better error messages for use of old restricted types #2764
Better error messages for use of old restricted types #2764
Conversation
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:feature/stable-cadence commit f9de789 Collapsed results for better readability
|
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## feature/stable-cadence #2764 +/- ##
=======================================================
Coverage 79.65% 79.65%
=======================================================
Files 339 339
Lines 80623 80652 +29
=======================================================
+ Hits 64219 64243 +24
- Misses 14104 14108 +4
- Partials 2300 2301 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
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.
Nice!
It might make sense to put this behind a feature flag and only enable it in the preview builds (e.g. "StableCadenceMigrationAssistanceEnabled
")
Currently it doesn't seem possible to selectively enable or disable parsing rules based on config options (i.e. |
It might be possible to add the option to The benefit of putting the feature behind a flag is that it makes it explicit, but it's also not important and maybe also not worth the effort. If it is too much of a hassle, maybe just leave a comment/TODO to eventually remove that code in again. |
Closes #2759
Restricted types have been removed, but parsing old code that uses them results in a confusing error. Add special handling for this case for now.
master
branchFiles changed
in the Github PR explorer