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

Changes to BlazeTargetFilter regex to match more target names #6021

Merged
merged 1 commit into from
Feb 12, 2024

Conversation

LeFrosch
Copy link
Collaborator

@LeFrosch LeFrosch commented Feb 5, 2024

Checklist

  • I have filed an issue about this change and discussed potential changes with the maintainers.
  • I have received the approval from the maintainers to make this change.
  • This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.

Discussion thread for this change

Issue number: #4431

Description of this change

Changed the regex used by BlazeTargetFilter to include more valid target names. I used this documentation page to lookup the valid characters.

@github-actions github-actions bot added product: CLion CLion plugin product: IntelliJ IntelliJ plugin product: GoLand GoLand plugin awaiting-review Awaiting review from Bazel team on PRs labels Feb 5, 2024
@ujohnny ujohnny merged commit 8a82231 into bazelbuild:master Feb 12, 2024
8 checks passed
@github-actions github-actions bot removed the awaiting-review Awaiting review from Bazel team on PRs label Feb 12, 2024
@ujohnny ujohnny linked an issue Feb 12, 2024 that may be closed by this pull request
@mmendonca2
Copy link

I think this issue created a problem where a top level exclusion "-someFolder" is now excluding that folder name from the entire project, no matter if it's nested in an explicitly included target. So now "includedTarget/someFolder" is excluded as well. It's problematic when explicitly excluding top level projects from .bazelproject whose name can show up in other targets as a package folder, as it breaks their builds.

@LeFrosch
Copy link
Collaborator Author

Hi @mmendonca2, as far as I can tell the BlazeTargetFilter is only registered using a consoleFilterProvider and not used any where else. Therefore, I think it is only used for highlighting links in the console.
If this is not the case and you are sure this is related to these changes please let me know. Otherwise, if this is a new issue please create an issue.

@ujohnny
Copy link
Collaborator

ujohnny commented Mar 28, 2024

I guess it is caused by #6094, @tpasternak haven't you mentioned something about this scenario to me several weeks ago?

@mmendonca2 could you please try specifying use_exclusion_patterns: false in project view file and perform sync?

@LeFrosch
Copy link
Collaborator Author

LeFrosch commented Apr 8, 2024

@ujohnny @tpasternak I can confirm, the exclusion of subdirectories @mmendonca2 mentioned seems to be caused by #6094.

Also, setting use_exclusion_patterns: false looks like a valid workaround.

@tpasternak
Copy link
Collaborator

So what's the exact directory name that has been excluded? I added the new projectview setting exactly for cases like this one

@tpasternak
Copy link
Collaborator

ok, we'll going to fix it soon

#6374

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product: CLion CLion plugin product: GoLand GoLand plugin product: IntelliJ IntelliJ plugin
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A hyperlink in terminal is wrong for a target which has dot in name
6 participants