-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 cquery to filter out incompatible targets #12935
Allow cquery to filter out incompatible targets #12935
Conversation
...com/google/devtools/build/lib/starlarkbuildapi/platform/IncompatiblePlatformProviderApi.java
Outdated
Show resolved
Hide resolved
Added @comius as Build API lead. My understanding is they should vet changes to the Starlark build API. FYI my personal opinion is this is a pretty good candidate for being part of the API. |
ed184e9
to
d2db797
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.
Overall this looks great to me!
I would hold off merging before getting @comius 's input. Depending on his schedule, feel free to ping this issue again to keep momentum up.
...com/google/devtools/build/lib/starlarkbuildapi/platform/IncompatiblePlatformProviderApi.java
Outdated
Show resolved
Hide resolved
This patch exposes the `IncompatiblePlatformProvider` to Starlark just enough that it can be used with `cquery`'s `platforms()` function. I added an example of this to the documentation. The motivation here is to let users filter out incompatible targets from queries that provide things like the list of targets to build for CI. This patch is minimal on purpose. It does not allow users to instantiate an `IncompatiblePlatformProvider` in Starlark. This may be added in a future patch to address a different use case.
d2db797
to
56170b4
Compare
@comius, are you interested in taking a look at this PR? |
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'll merge... |
This patch exposes the `IncompatiblePlatformProvider` to Starlark just enough that it can be used with `cquery`'s `platforms()` function. I added an example of this to the documentation. The motivation here is to let users filter out incompatible targets from queries that provide things like the list of targets to build for CI. This patch is minimal on purpose. It does not allow users to instantiate an `IncompatiblePlatformProvider` in Starlark. This may be added in a future patch to address a different use case. Fixes #12917. Closes #12935. PiperOrigin-RevId: 356580943
This patch exposes the `IncompatiblePlatformProvider` to Starlark just enough that it can be used with `cquery`'s `platforms()` function. I added an example of this to the documentation. The motivation here is to let users filter out incompatible targets from queries that provide things like the list of targets to build for CI. This patch is minimal on purpose. It does not allow users to instantiate an `IncompatiblePlatformProvider` in Starlark. This may be added in a future patch to address a different use case. Fixes #12917. Closes #12935. PiperOrigin-RevId: 356580943
This patch exposes the
IncompatiblePlatformProvider
to Starlark justenough that it can be used with
cquery
'splatforms()
function. Iadded an example of this to the documentation. The motivation here is
to let users filter out incompatible targets from queries that
provide things like the list of targets to build for CI.
This patch is minimal on purpose. It does not allow users to
instantiate an
IncompatiblePlatformProvider
in Starlark. This may beadded in a future patch to address a different use case.
Fixes #12917.