Skip to content
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

Distinguish between library and plugin IDs in component dependencies #1912

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

scarb/src/compiler/compilation_unit.rs Outdated Show resolved Hide resolved
Comment on lines +98 to +102
/// Checks whether the [`CompilationUnitComponent`] represents a plugin package.
pub fn is_cairo_plugin(&self) -> bool {
self.package.is_cairo_plugin()
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can component ever be a plugin? cc @maciektr

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose components representing procedural macros will return true here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, @maciektr suggested adding this function (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants