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

refactor(gazelle): Move plugin to a separate directory. #983

Merged
merged 1 commit into from
Jan 24, 2023

Conversation

aignas
Copy link
Collaborator

@aignas aignas commented Jan 12, 2023

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature (please, look at the "Scope of the project" section in the README.md file)
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

@alexeagle requested to split #972 into multiple PRs for easier review, so this is the first part.

Issue Number: #965

What is the new behavior?

This is in order to make #972 easier to review. This PR is only moving files and addressing a few small review comments made in the initial review of #972. I have also made alias targets to make this a non-breaking change from the user point of view in case a release is made before the breaking change of introducing the new WORKSPACE is merged.

Work towards #965.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@aignas aignas requested a review from f0rmiga as a code owner January 12, 2023 04:36
@aignas aignas force-pushed the gazelle-move-plugin-to-dir branch 2 times, most recently from 6257e87 to b7743a9 Compare January 12, 2023 04:46
@aignas
Copy link
Collaborator Author

aignas commented Jan 19, 2023

@f0rmiga, could you please take a look when you have time?

@alexeagle
Copy link
Collaborator

Well, now I'm a bit confused because we just added "optional" dependencies https://github.com/bazelbuild/rules_python/blob/main/MODULE.bazel#L9-L11
that not all users of rules_python need. Maybe these two are just harmless in a way that rules_go isn't?

@aignas
Copy link
Collaborator Author

aignas commented Jan 20, 2023

I somewhat still think that having this refactoring in won't hurt, given that once it is done we can either way - a single MODULE.bazel or multiple.

Copy link
Collaborator

@f0rmiga f0rmiga left a comment

Choose a reason for hiding this comment

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

Could you resolve the conflicts, please?

This is in order to make bazelbuild#972 easier to review. This PR is only moving
files and addressing a few small review comments made in the initial
review of bazelbuild#972.

Work towards bazelbuild#965.
@f0rmiga f0rmiga merged commit 0ee2a7e into bazelbuild:main Jan 24, 2023
@aignas aignas deleted the gazelle-move-plugin-to-dir branch January 24, 2023 08:40
ianpegg-bc pushed a commit to ianpegg-bc/rules_python that referenced this pull request May 12, 2023
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.

None yet

3 participants