tree b1a0811f0242a8e7edfd0cc0618350ca8afc4987
parent ce749147a9a4f8fc8ef6141bf34ab538ed7f7476
author Ignas Anikevicius <anikevicius@gmail.com> 1682962497 +0900
committer GitHub <noreply@github.com> 1682962497 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkT/hBCRBK7hj4Ov3rIwAAPUEIABq58hh4mChJMoMnsSQp0dG9
 DvWeKyItiaYlvALkHcMA855ClRljfpR/UOu9yct7h1nd9jfHdL5Ws7FcOvCcg5Qe
 F4ZBQboUVYHfFgilBEQtBkXCpeunV/wr6aJD+IQ6DkVWJfFx+OzYSBfJidiCTpCN
 QwNZ6FD1V4qjcjkGXwrqJc80LuoSTYmYNBfJ9KVwd1ogUnjDGzm4QEYhKS8QvAAr
 z7ZaeD6C4nvCQEKjLeD12MATNnFxs97Ll4aKvicNj5SNqMJ5SZm5VKDhaWxTlDVk
 heXPmZR8fOxW+NlxfCQhO98wZ+5wdKUS+Kr0ztAR0TYzlHGchxGU0Hzaa1Hu9HU=
 =c34D
 -----END PGP SIGNATURE-----
 

fix(bzlmod): correctly template repository macros for requirements, etc (#1190)

It seems that the macros for specifying the requirements break when the
user starts using `incompatible_generate_aliases=True`. This PR fixes
this.

Testing done:
1. Modify the example:
   ```
   $ git diff
diff --git a/examples/bzlmod/MODULE.bazel b/examples/bzlmod/MODULE.bazel
   index ce91228..1750210 100644
   --- a/examples/bzlmod/MODULE.bazel
   +++ b/examples/bzlmod/MODULE.bazel
   @@ -26,6 +26,7 @@ register_toolchains(
    pip = use_extension("@rules_python//python:extensions.bzl", "pip")
    pip.parse(
        name = "pip",
   +    incompatible_generate_aliases=True,
        requirements_lock = "//:requirements_lock.txt",
        requirements_windows = "//:requirements_windows.txt",
    )
   ```
2. Run `bazel build ...` and check that it is still working.

I noticed this when working on #1189 and creating a separate PR for
easier cherry-picking if we wanted to make a patch release which
includes this. I am not sure how I could make an automated test for this
other than creating a separate example.