Filter Transaction list based on Request Body contents

⚠️ Is your feature request related to a problem? Please describe

We are using Chucker to inspect our https requests & responses and that also includes GraphQL. But due to the diverse and numerous modules in our application making network requests, the transaction list can sometimes become huge. Filtering on the basis of the URL doesn’t help because the endpoints for all the GraphQL requests are just the same(because all our GraphQL requests are POST requests).
Filtering the transaction list on the basis of the request body content would be extremely helpful to filter specific transactions not limited to just GraphQL.

💡 Describe the solution you’d like

A very naive solution, without requiring any UI change, would be to update the SQL query in the HttpTransactionDao’s getFilteredTuples() function to search the user entered text in the request body as well. Eventually updating the query to:-

 "SELECT id, requestDate, tookMs, protocol, method, host, " +
            "path, scheme, responseCode, requestPayloadSize, responsePayloadSize, error, isGraphQLRequest FROM " +
            "transactions WHERE responseCode LIKE :codeQuery AND (path LIKE :query " +
            " OR requestBody LIKE :query) ORDER BY requestDate DESC"

📊 Describe alternatives you’ve considered

Nothing so far.

📄 Additional context

🙋 Do you want to develop this feature yourself?

• Yes
• No

[cortinico]

Filtering the transaction list on the basis of the request body content would be extremely helpful to filter specific transactions not limited to just GraphQL.

I’m afraid this feature will actually have unwanted side effects. Specifically:

1. You might end up not really filtering the list. As we widen the search surface, the result list can increase and reduce the effectiveness of the filter.
2. Users might not really understand why a certain transaction is shown. HTTP Body can be really complex, with both request and response, so users won’t really know why a certain transaction is show, till they effectively open it and look through the bodies.

I see your use case though, so I’m not totally against this. I think we should consider it somehow, but I’d like to collect more opinions on this.

[cortinico]

What sort of timeline are we looking at for the next release?

Whenever we have time 😦 I’m extremely busy at the moment. We’re looking for other maintainers also 😃