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

Do not assume a config can be empty #1455

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

travjenkins
Copy link
Member

@travjenkins travjenkins commented Feb 6, 2025

Issues

#1454

Changes

1454

  • I think we should always assume the config must provide some fields until we are proven otherwise. I am not totally sure why we went with this default.

Tests

Manually tested

  • scenarios you manually tested

Automated tests

  • unit testing covered

Playwright tests ran locally

  • Admin
  • Captures
  • Collections
  • HomePage
  • Login
  • Materialization

Screenshots

Before the change
Image

After the change
Image

return false;
}

return Boolean(!schema.properties || isEmpty(schema.properties));
Copy link
Member Author

Choose a reason for hiding this comment

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

Pretty sure this introduced the ability for a race condition

https://github.com/estuary/ui/pull/1230/files#r1729428622
image

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.

1 participant