-
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
Relocate advanced materialization settings in workflows #1417
Relocate advanced materialization settings in workflows #1417
Conversation
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.
lgtm
const fullSourceErrorExists = useBindingStore((state) => { | ||
const fullSourceErrors = state.fullSourceConfigs[bindingUUID]?.errors; | ||
|
||
if (!fullSourceErrors) { | ||
return false; | ||
} | ||
|
||
return fullSourceErrors.length > 0; | ||
}); | ||
|
||
const onIncompatibleSchemaChangeErrorExists = useBindingStore( | ||
(state) => state.onIncompatibleSchemaChangeErrorExists.binding | ||
); |
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.
Do not need to change for this PR... but I think it would be safe to put these two into a single shallow
call. I think that might help reduce how often these might change.
setOnIncompatibleSchemaChangeErrorExists: (value, key) => { | ||
set( | ||
produce((state: BindingState) => { | ||
state.onIncompatibleSchemaChangeErrorExists[key] = value; | ||
}), | ||
false, | ||
'On Incompatible Schema Change Error Exists Set' | ||
); | ||
}, |
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.
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.
lgtm - previous one I thought I was marking another PR 🤦
…erialization-settings
Issues
The issues directly below are completely resolved by this PR:
#1416
Changes
1416
The following features are included in this PR:
Add an Advanced Options accordion section to the Source Collections form section to hide the specification-level
onIncompatibleSchemaChange
field.Add an Advanced Options accordion section at the bottom of the Config tab in the binding selector to hide the binding-level
onIncompatibleSchemaChange
and time travel fields.Update the Source Collections section description of the materialization edit workflow to the following:
The collections bound to your materialization. Update configuration under the Endpoint Config tab.
This content change request is made in the linked issue.Tests
Manually tested
Approaches to testing are as follows:
Validate that the capture workflows remain unchanged.
Validate that the
onIncompatibleSchemaChange
and time travel functionality remain unchanged.Validate that the specification-level
onIncompatibleSchemaChange
field appears in the Advanced Options accordion section located within the Source Collections form section.Validate that the binding-level
onIncompatibleSchemaChange
field appears in the Advanced Options accordion section located at the bottom of the Config tab in the binding selector.Automated tests
N/A
Playwright tests ran locally
Screenshots
Materialization Create Workflow
Specification-level Advanced Options | Closed
Specification-level Advanced Options | Open
Materialization Edit Workflow
Source Collections section description in materialization edit workflow
Specification-level Advanced Options | Closed
Specification-level Advanced Options | Open
Binding-level Advanced Options | Closed
Binding-level Advanced Options | Open