fix: fetch updates on the detail page when change events are received #6938
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
for ENTESB-11405
@claudio4j this is what I was thinking in regards to the server events.
Looking deeper I think I led you astray a bit,
useConnection
returns aread()
function that can be used to trigger a fetch, so another option would have been to callread()
after calling the save function. But this approach should work as well, after going through the oauth dance once there's a change made to the connection the UI should then fetch an updated connection.I can't seem to fully see this working in development mode though, it seems like the dev proxy isn't receiving the change events for some reason. Can you test this in your environment? You'd want to build the console and deploy it to verify I think, open the network tab and you should see a
GET
occur shortly after the ui does thatPUT
.