-
```
When using myopenid.com as provider, the response validation performed by
LightOpenID will fail under certain conditions.
It seems to fail when I request the "namePerson" attribute and the value…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Description
When using Input-Group inside a form, the error message comes between the input and the button, if…
-
### Describe the bug
I am unable to set my `limit` for a `RateBasedStatementProperty` below 100. Attempting to do so results in a stack error:
```
Resource handler returned message: "Model valida…
-
```
When using myopenid.com as provider, the response validation performed by
LightOpenID will fail under certain conditions.
It seems to fail when I request the "namePerson" attribute and the value…
-
```
When using myopenid.com as provider, the response validation performed by
LightOpenID will fail under certain conditions.
It seems to fail when I request the "namePerson" attribute and the value…
-
```
When using myopenid.com as provider, the response validation performed by
LightOpenID will fail under certain conditions.
It seems to fail when I request the "namePerson" attribute and the value…
-
1. Uncomment `# config.middleware.use Committee::Middleware::ResponseValidation, schema_path: 'openapi.yml'` in `config/application.rb`
1. Run the specs and watch the failures
1. Fix the failures
-
### NextUI Version
2.4.8
### Describe the bug
`Input` and `Select` validation behaviour is different.
### Your Example Website or App
_No response_
### Steps to Reproduce the Bug or Issue
When…
-
### Description
It may be the case that the feature is abandoned, but the macros seem to be widely ignored and instead the symbols are just typed from the namespace `nlohmann` or, `::nlohmann`
### R…
-
```
When using myopenid.com as provider, the response validation performed by
LightOpenID will fail under certain conditions.
It seems to fail when I request the "namePerson" attribute and the value…