Remove the need for experimentalMacroSupport and gate on SDK version #5105
Labels
Milestone
Comments
DanTup
added a commit
that referenced
this issue
May 13, 2024
This will allow macros to be controlled just by the SDK experiment flags and not require an additional VS Code setting. It will only enable for >= 3.5.0-0 (current bleeding edge) since that's the only place macros work well enough to try out. Fixes #5105
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
dart.experimentalMacroSupportsetting was used to enable new APIs to get generated code from the server into VS Code. There's been enough testing that this flag is probably unnecessary now, however we should gate enabling these new APIs on a suitable version number where this API support is more stable/complete (perhaps 3.5.0-0, since 3.5 is what current bleeding-edge builds are).The text was updated successfully, but these errors were encountered: