-
Notifications
You must be signed in to change notification settings - Fork 12
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
Choose custom router on subnet create/edit forms #2393
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…will have to be reverted.
96196ea
to
b4e9277
Compare
b4e9277
to
5b1dd2a
Compare
await expect(rows.nth(1).getByText('10.1.1.2/24')).toBeVisible() | ||
// little hack to catch a bug where we weren't handling empty input here properly | ||
await dialog.getByRole('textbox', { name: 'IPv6 block' }).fill('abc') | ||
await dialog.getByRole('textbox', { name: 'IPv6 block' }).clear() |
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.
I think this is solid. I like the string sentinel value pattern for a clearable listbox. It might make sense to build this logic into the listbox field itself somehow, so we don't have to manually wire up the conversion between form values and JSON values. On the other hand, it seems like the way we're doing it is kinda how you're supposed to do it — RHF doesn't seem to like it when you try to store the processed maybe-not-a-string value in the form state.
Add a field on the subnet create/edit form, enabling linking a custom router to the subnet.
Fixes #2379