Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain changes between requests #3

Open
g105b opened this issue Nov 3, 2023 · 0 comments
Open

Explain changes between requests #3

g105b opened this issue Nov 3, 2023 · 0 comments
Milestone

Comments

@g105b
Copy link
Owner

g105b commented Nov 3, 2023

The current implementation shows a list of responses associated to the current request, which only really makes sense if none of the parameters change on the request between responses.

If I create a request, execute it so I can see the response, and then change something like the query strings or method, what should happen to the existing responses? They could be deleted, but I think it would be better to keep them, but show what's changed.

This can be done using bindListCallback() here instead of bindList(). The ResponseEntity will need to take a reference of the RequestEntity in the constructor (like it used to), and then for each iteration it can check what's difference, and list out the changes to the page.

@g105b g105b added this to the v1 milestone Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant