-
Notifications
You must be signed in to change notification settings - Fork 556
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
Allow downstream macros #3779
base: main
Are you sure you want to change the base?
Allow downstream macros #3779
Conversation
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 out of the loop. @tarrencev are you able to declare these macros in Dojo via the mechanism that already exist in Scarb? |
Hmm I wasn't aware of a mechanism in scarb, do you mind sharing more? |
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.
I meant the CairoPluginRepository thingy that you use for the semantic plugin. Are you able to use InlineMacros via it or do you miss something on Scarb's side also here?
Reviewable status: 0 of 2 files reviewed, all discussions resolved
Oh yes we are using that but the core inline macro plugin is registered earlier in the pipeline and emits a diagnostic for any macro it doesn't understand. From what I can tell, it isn't possible to register our inline macro plugin before the core implementation? |
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.
Yeah, your understanding is correct and this PR is definitely needed :) I was really just asking for feedback if you are able to push your plugins to Scarb :)
Reviewable status: 0 of 2 files reviewed, all discussions resolved
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.
Reviewable status: 0 of 2 files reviewed, 1 unresolved discussion (waiting on @tarrencev)
a discussion (no related file):
No longer relevant - was merged into dev-v2.1.0 and no longer relevant on main as well.
Similar to how we allow downstream derives for now
This change is