Skip to content
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

Postgres capture bindings are not defaulting properly #1255

Open
travjenkins opened this issue Sep 11, 2024 · 0 comments
Open

Postgres capture bindings are not defaulting properly #1255

travjenkins opened this issue Sep 11, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@travjenkins
Copy link
Member

travjenkins commented Sep 11, 2024

Bug1
New capture
select postgres
Enter endpoint config
Discover
Get results
See the next button show

Expected
The next button does not show


Bug 1
Create / publish a postgres capture with at least 2 bindings
Edit same capture
Click on second binding in resource config editor
See the next button appear because mode was defaulted to an empty string ""

Expected
The next button does not display
The field is not defaulted to an empty string

Screenshots
The initial discover is not defaulting mode to an empty string on the backend
image

Desktop (please complete the following information):
N/A

Additional context
Might end up being an issue we just have to deal with

@travjenkins travjenkins added the bug Something isn't working label Sep 11, 2024
@travjenkins travjenkins changed the title Changing binding while editing Postgres Capture can edit spec Postgres capturre bindings are not defaulting properly Sep 11, 2024
@kiahna-tucker kiahna-tucker changed the title Postgres capturre bindings are not defaulting properly Postgres capture bindings are not defaulting properly Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant