Conversation
…lected and the user is not allowed to change it later
Handling errors when fetching Cleaning up the unsupported stuff
new context blocks showing the entire flow if there isn't a connector
Adding in fetching 500 so we don't need pagination Updating typing now that my local has latest merged on flow
…that has been handled
it a pretty safe page to allow hitting.
| setDraftId(null); | ||
| setInitiateDiscovery(true); | ||
| }, [setDraftId, setInitiateDiscovery, imageTag]); | ||
|
|
There was a problem hiding this comment.
Since we prevented users from changing the connector awhile ago I think this is totally safe to remove.
| const q = searchQuery.toLowerCase(); | ||
| return nodes.filter( | ||
| (node) => | ||
| node.title?.toLowerCase().includes(q) || | ||
| node.shortDescription?.toLowerCase().includes(q) | ||
| ); |
There was a problem hiding this comment.
We now need to do some of the filtering client side.
There was a problem hiding this comment.
We used to need to set stuff here but seems it is good now.
Only thing to call out is the setConnector used to have a side effect of setting setEntityNameChanged. I think Kiahna is right and this was back when the connector could change and we needed to set the name changed because the connector being suffixed was going to change.
Adding basic eventing in Handling exceptions
There was a problem hiding this comment.
Connector folks could use the jsonforms test page in prod.
There was a problem hiding this comment.
New basic guard for support role. Potentially we'l add a special error or something here but not major concern right now.
| ); | ||
|
|
||
| export const MAC_ADDR_RE = new RegExp(/^([0-9A-F]{2}:){7}([0-9A-F]{2})$/i); | ||
| export const MAC_ADDR_LIKE_RE = new RegExp(/^([0-9A-F]{2}){7}([0-9A-F]{2})$/i); |
There was a problem hiding this comment.
GQL returns UUIDs without the colon vs Postgrest that returns the UUIDs with colons.
connectors over to using GQL
Issues
#1929
Changes
issue_number
useConnectorTagcontext.hasValidConnectorshook we used to need.test/jsonformsis now available in productionunsupportedConnectoras we just fired an event for that and didn't show anything to the user.detailshydrator as only the test page was using thatTests
Manually tested
Automated tests
Playwright tests ran locally
Screenshots
Edit now shows the connector image tag in the URL
