Skip to content

Conversation

@zsomborkincses
Copy link

Reopened a feature request that has been opened by @AnOtterGithubUser and abandoned (1467) based on the issue: 1466

Included changes based on the review of @Ekrekr

…ctions which include all tags in --tag option
@zsomborkincses zsomborkincses requested a review from a team as a code owner May 14, 2025 13:15
@zsomborkincses zsomborkincses requested review from kolina and removed request for a team May 14, 2025 13:15
@google-cla
Copy link

google-cla bot commented May 14, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@Ceridan Ceridan requested review from Ceridan and removed request for kolina June 5, 2025 15:05
Copy link
Contributor

@Ceridan Ceridan left a comment

Choose a reason for hiding this comment

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

Thank you for your contribution!


const hasActionSelector = runConfig.actions?.length > 0;
const hasTagSelector = runConfig.tags?.length > 0;
const hasFlterTagsAsIntersectionSelector = runConfig.filterTagsAsIntersection?.valueOf();
Copy link
Contributor

Choose a reason for hiding this comment

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

Instead of runConfig.filterTagsAsIntersection?.valueOf() I suggest to use !!runConfig.filterTagsAsIntersection

There is also a typo in the word Filter.

}
};

const flterTagsAsIntersectionSelectorOption: INamedOption<yargs.Options> = {
Copy link
Contributor

Choose a reason for hiding this comment

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

typo in the word "filter"

};

const flterTagsAsIntersectionSelectorOption: INamedOption<yargs.Options> = {
name: "filter-tags-as-intersection",
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's make it shorter for the user. Maybe just tags-intersection, WDYT?

test("prune actions with --tags (with include all tags)", () => {
const prunedGraph = prune(TEST_GRAPH_WITH_TAGS, {
tags: ["tag1", "tag2"],
includeAllTags: true
Copy link
Contributor

Choose a reason for hiding this comment

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

filterTagsAsIntersection?

Comment on lines +380 to +383
expect(actionNames).not.includes("schema.op_a");
expect(actionNames).not.includes("schema.op_b");
expect(actionNames).not.includes("schema.op_c");
expect(actionNames).not.includes("schema.op_d");
Copy link
Contributor

Choose a reason for hiding this comment

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

We already made a deep.equals on previous line, we do not need to double check this with not.include

@Ceridan
Copy link
Contributor

Ceridan commented Jul 2, 2025

@zsomborkincses do you plan to work on this? Otherwise I will close the PR.

@Ceridan
Copy link
Contributor

Ceridan commented Jul 15, 2025

Closing this because there is no response from the PR author.

@Ceridan Ceridan closed this Jul 15, 2025
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.

2 participants