apis

Hi community

This message is to clarify and make transparent the current situation of Public APIs, in addition to demonstrating the frustration of us maintainers. So read this if you find it interesting, please.

Well, I keep the Public APIs project together with other 3 developers (@pawelborkar, @marekdano and @yannbertrand) for a long time.

1 year ago, the Public APIs project was dead, w

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

Hello! We had a need for the "does not contain" pattern while using your tool.

Usage example :
We have multiple query parameters "groups" in a URL: http://localhost:1111/test-stub?groups=Qwerty&qroups=Qwerty2

So we need to do something like

...
"id" : "c459a482-5b18-4c12-a17f-be2834fd6cdf",
"name" : "mapping-name",
 "request" : {
      "urlPath" : "/test-stub",
      "metho

Describe the event source. What app is this for, and what event does the trigger correspond to?
Find streams by title in category
Please provide a link to the relevant API docs for the specific service / operation this trigger is tied to.

Description

This ws used to return a map of DP versions --> Envoy versions. We now have a more systematic and logical way to do this and we can remove this service altogether.

Right now the tutorial is coherently designed, tested, and even documented. However, it doesn't build up in a way that's very beginner friendly. It establishes glom's value and then immediately uses it at an intermediate level.

I'd like it if it was a bit more drawn out to use basic features first and then add a multi-line Coalesce as the

As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.

The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh

Describe your problem(s)

In the "Complexity Analysis" tab in GraphQL try-out page in devportal, we can see only the complexity Values of each field. If we want to know the complexity value or the depth value, we have to calculate ourself manually. Instead, it would be a nice to have feature to have the possibility to display the calculated complexity/depth values on a button click. So before

The fastapi example (and perhaps the others) are a little misleading to newbies.

The following lines would suggest that there is pact mock on the provider side, when in reality this is the address of the locally running FastAPI provider:

PACT_MOCK_HOST = 'loca