-
Notifications
You must be signed in to change notification settings - Fork 26
Introduced a monitoringClient and serviceControlClient #2725
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
Conversation
d0cad1d to
6fb9a65
Compare
Introduced a monitoringClient
f692f92 to
0efe289
Compare
src/Frontend/src/components/configuration/EndpointConnection.vue
Outdated
Show resolved
Hide resolved
| localMonitoringUrl.value += "/"; | ||
| } | ||
| //values have changed. They'll be reset after page reloads |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my understanding is that these values are used in determining the url that's actually used in the SC and monitoring clients, so wouldn't this logic still be necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is now handled in the client getUrl?
const existingScu = window.localStorage.getItem("scu");
if (scu) {
if (scu !== existingScu) {
window.localStorage.setItem("scu", scu);
}
return scu;
}# Conflicts: # src/Frontend/src/components/failedmessages/DeletedMessages.vue # src/Frontend/src/components/failedmessages/FailedMessages.vue # src/Frontend/src/components/failedmessages/PendingRetries.vue # src/Frontend/src/stores/ServiceControlStore.ts
This PR separates the client APIs from the store.
So, in this PR we make the separation to use the store as just a state management store, and the calling of the REST api is delegated to the client api.