-
Notifications
You must be signed in to change notification settings - Fork 6.8k
build: group examples by package and entry-point name #16822
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
build: group examples by package and entry-point name #16822
Conversation
f2afdcd
to
08cee99
Compare
Groups the examples by package and entry-point name. This allows us have a bazel build target for each group and also allows us to separate MDC prototypes from standard implementations.
08cee99
to
4cf8325
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.
LGTM
EXAMPLE_PACKAGES = [ | ||
# TODO(devversion): try to have for each entry-point a bazel package so that | ||
# we can automate this using the "package.bzl" variables. | ||
"//src/material-examples/cdk/a11y", |
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.
For a follow-up, we should probably split this is into src/material-examples
and src/cdk-examples
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.
Yes that was one of the ideas when I made separate directories 😄 It just involves a bit more work for now since our docs only expect one examples package right now.
Groups the examples by package and entry-point name. This allows us have a bazel build target for each group and also allows us to separate MDC prototypes from standard implementations. (cherry picked from commit d3a9a20)
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Groups the examples by package and entry-point name. This
allows us have a bazel build target for each group and also
allows us to separate MDC prototypes from standard implementations.