Skip to content

SC-408 Node Connections helper functions#860

Open
nbeatty-gpa wants to merge 5 commits into
masterfrom
SC-408
Open

SC-408 Node Connections helper functions#860
nbeatty-gpa wants to merge 5 commits into
masterfrom
SC-408

Conversation

@nbeatty-gpa
Copy link
Copy Markdown
Contributor

Restructures the helper functions which make network requests to check XDA and System Center connections, making them pure functions outside of the NodeConnections component which return promises, allowing the network requests to be cleaned up.

Also removes the unused Status state.

Jira Work Item(s)

  • SC-408

@nbeatty-gpa nbeatty-gpa force-pushed the SC-408 branch 2 times, most recently from 8f90fc2 to 5ca1041 Compare May 29, 2026 13:30
Comment on lines 44 to 49
const dbs = testDBs()
dbs.done((statuses: INamedStatusItem[]) => {
setExtDBStatus(statuses)
}).fail((d) => {
}).fail(() => {
setExtDBStatus([])
})
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the component-level status state removed, loading now seems to be represented only by the initial Status: "Loading" values in NodeConnections. Are these API responses ever expected to return Status: "Loading", or should NodeConnections reset its own items to loading before each refetch? I’m mostly wondering about stale status display while a new request is in flight.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good point, the API never returns `Status: "Loading" so I'll look at resetting the items before a refetch.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed 02bb75c

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

Successfully merging this pull request may close these issues.

2 participants