Hi there! I have a question regarding structuring ...
# pactflow
d
Hi there! I have a question regarding structuring contracts within pactflow. Am I correct that on the left side the user can see the highest level of the communication between consumer & provider? All endpoints & interactions for these participants are grouped there. This means that when the user opens the detail page of the contract which may have a long list of endpoints to cover in the pact he would see a long list with interactions and endpoints. So, i was wondering if there is a way to structure all interactions per endpoint and not present the full list of interactions for all endpoints between consumer and provider. Thanks!
đź‘‹ 1
m
Interesting idea. We are looking at some redesign at the moment, and will see how this migth be able to inform that design. cc: @Shuying Lin
Knowing the endpoint isn’t always straightforward, but might be doable. There are possibly other ways to group as well
d
Is there a way to group it on the left side for every endpoint? So having a pact for each endpoint which be somehow grouped for one consumer & provider pair via the teams feature. Or what would be other ways on your eyes? Thanks Matt. :)
m
you can group integrations by team, but I think you want it for the interaction level
What is an “endpoint” to you? It has very different meanings to different people!
e.g. it could be
product
the first path segment of
/products/1
/orders/:id
- we’d probably all agree that’s orders.
/orders/:id/items
- is that orders or items?
/orders/:id/items/:id/actions
- is that orders or items or something else?
It gets trickier too, because you may not easily be able to detect the dynamic parts of the request without a number of samples (and even then, it’s risky). Probably numbers are placeholders, but not necessarily. Harder for strings
d
I see. That’s more complex than I thought. In your example I would expect
product
to be the highest level which groups all interactions in it.