Using "useRegExpForFields" makes the docs spin and queries don't go through.

[Davenporten]

My gut reaction to the following problem was to report a bug, but after seeing that other people seem to be using the useRegExpForFields without a problem I thought maybe I was just missing something in my .meshrc.yaml. So here's the situation: I have two different graphql API that I have my meshrc is pointing to. I want to transform each query to have query_ appended to the beginning of queries that come in from the API (I know there is a prefix transform, but that 1) is more general than I need, and 2) this is kind of an example, my problem is that I can't get the regex renaming to work). To do this I have the following in my mechrc:

transforms:
  - rename:
      mode: wrap | bare
      renames:
        - from:
            type: Query
            field: employee(.*)
          to:
            type: Query
            field: query_$1
          useRegExpForFields: true

The to field regex is probably wrong (is this the issue?), I've just been going off of what is in the example in the docs: https://www.graphql-mesh.com/docs/transforms/rename#how-to-use

When I run this though the docs spin forever

and autocomplete for the queries field doesn't work anymore. Maybe it's just running the regex still? If that's the case I still haven't seen it end.

Anyway, any thoughts or direction on this would be much appreciated. Thanks in advance!

[santino]

Your config looks right.

The only thing I can clearly see is that you need to pick up a mode for the transform, effectively choosing either "bare" or "wrap".
Given you are working with GraphQL sources, actually you don't have a choice, you need "wrap" mode.

As such I suggest removing this line completely mode: wrap | bare since "wrap" mode is applied by default.

For more info, take a look at the docs here:
https://www.graphql-mesh.com/docs/getting-started/mesh-transforms#two-different-modes

[Davenporten]

Thanks for the reply!

So I tried what you suggested and was still getting the same result and then just not knowing what to do I set the mode to bare and it started to work. Of course, just as you suggested, this shouldn't be the case. I've tried placing the transform in the sources themselves, but same result: I needed to get mode to bare. The doc you sent is pretty clear that this shouldn't be working, but for whatever reason is the only thing that's working. I wonder if it has anything to do with my services that the .meshrc is pointing to are build with the DGS Framework. I don't know why this would be as they deliver typical graphql schemas, but I feel like it's either that or there is some off in the docs.

[Davenporten]

I think I may open a bug for this as it's pretty clear this is a disconnect between what the docs say and what is working for me.

[santino]

Probably that's normal.

I suppose you're setting the transform on the root level and not on the source level.
In this case "bare" makes sense.

If you apply the transform on the source level, you will see that it will need to work in "wrap" mode; given it's a GraphQL source.

Can you try and confirm?

[Davenporten]

Sorry Santino, I created that bug-issue before seeing your reply. I had tried that with the same result. If bare is in there the docs are generated, but the queries don't seem to go through, and with wrap the docs just spin.

[Davenporten]

Yeah, it seems like this is the problem: with bare the docs are generated, but the renamed query won't work as the service its pointed at doesn't recognize it; and with wrap the renaming process getting into what looks like an infinite loop.