Validate button is disabled in API connector
See original GitHub issueThis is a…
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Documentation issue or request
Description
The validate
button is disabled no matter what field I change. And the next button is disabled as well, I figured that it probably gets enabled when the connector is validated.
Steps to reproduce:
- import API client specification (https://petstore.swagger.io/v2/swagger.json)
- go into connections and try to create that connector
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
Validate Button on Mapping Transformations are Disabled ...
This issue may occur due to browser cache not being cleared. 1) For Solution, enter CR with a Workaround if a direct Solution...
Read more >Disable/Enable Button in Blazor - Depending on what is in the ...
I've got this one razor page in which I put some data in (Name, FamilyName etc.) and then I click Send, the data...
Read more >Submit button disabled until all form fields are valid. #1996
Hi, Great plug-in. Is there a way of initially setting the Form Submit button to disabled and it is only enabled when all...
Read more >Frustrating Design Patterns: Disabled Buttons
Some people will want to verify that the button is indeed disabled, by hovering over it, trying to click/tap on it, or tab...
Read more >Should form 'Continue' button be disabled if validation is ...
Yes the "Continue" button should be disabled until all required fields are filled out with at least some text ( ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t think we have any way to know that something can’t be validated against the BE right now.
Verified by QE