-
Notifications
You must be signed in to change notification settings - Fork 2
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
Using update_only
when doing background discover and content change
#955
Conversation
…ting collections and not adding NEW ones.
update_only
when doing background discover and content change
Setting update only if editing without changing endpoint
Passing data so we don't get weird issues with heights
…avjenkins/uxTweaks4
Storing off what rows are open
const { generateCatalog, isSaving, formActive } = useDiscoverCapture( | ||
entityType, | ||
{ | ||
// We only want to set updateOnly if the user is editing and not updating the config |
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.
and not updating the config
Given the presence of the useResourceConfig_rediscoveryRequired
hook above, it should be clear that the resource config is what is being referred to by the term config. However, it could not hurt to explicitly state that updateOnly
should be set if the user (clicked the Next CTA and) did not change the resource config in an edit workflow.
const { generateCatalog, isSaving, formActive } = useDiscoverCapture( | ||
entityType, | ||
{ | ||
// We only want to set updateOnly if the user is editing and not updating the config | ||
// This should cover when a user has enable previously disabled collection(s) |
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.
a user has enable previously disabled collection(s)
Removing the passive voice from this comment will increase its clarity: This should cover when a user enables previously disabled collection(s).
if (discoverResponse.error) { | ||
// If we failed at discovery we need to clear draft ID like we do |
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.
This comment is a little muddled to me. What do you think of the following:
// If discovery fails, clear the draft ID to preserve the _Next_ CTA and allow the user to attempt to discover another time.
@@ -21,7 +21,7 @@ function MessageCell({ fields, message }: Props) { | |||
</Typography> | |||
|
|||
{fields ? ( | |||
<Typography component="div" sx={BaseTypographySx}> | |||
<Typography component="div" sx={{ ...BaseTypographySx }}> |
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.
The spread operator should not be needed here.
Issues
#953
#954
Changes
953
954
update_only
column based on if we are rediscoveringupdate_only
when discoveringMisc
Tests
Manually tested
Automated tests
Screenshots
Edit content updated

Create Content not changed

Clicking the

refresh
button still wants to do a discover so the user can get new items