Checkbox and radio buttons must be assigned a name prop when they are created, otherwise standard HTML treats them all as a single group. If a radio and checkbox component (or multiple) are created within the same page and they happen to have a value that's identical across both components, the pages will trigger incorrect behavior across both components. Adding a required name prop to both the Checkbox and Radio component functions should fix this issue.
Checkbox and radio buttons must be assigned a `name` prop when they are created, otherwise standard HTML treats them all as a single group. If a radio and checkbox component (or multiple) are created within the same page and they happen to have a value that's identical across both components, the pages will trigger incorrect behavior across both components. Adding a required `name` prop to both the `Checkbox` and `Radio` component functions should fix this issue.
Hi @hparihar-07! I didn't realize that anyone was even looking at this repository. If you've got a suggestion, feel free to fork this and send a PR. I haven't really cleaned up the pages and I don't necessarily have the time to get you set up properly, but I've tried to document the setup process. Also, a fair warning that I can't give you access to the real data - you'll have to make and use your own AWS account with the correct DynamoDB tables set up if you'd like to test with data.
Let me know if you find a solution to this, or if you're not interested anymore (I know it's been a while) then I or @meraghon will take it over ourselves.
> Hey 👋 Can I fix this issue?
Hi @hparihar-07! I didn't realize that anyone was even looking at this repository. If you've got a suggestion, feel free to fork this and send a PR. I haven't really cleaned up the pages and I don't necessarily have the time to get you set up properly, but I've tried to document the setup process. Also, a fair warning that I can't give you access to the real data - you'll have to make and use your own AWS account with the correct DynamoDB tables set up if you'd like to test with data.
Let me know if you find a solution to this, or if you're not interested anymore (I know it's been a while) then I or @meraghon will take it over ourselves.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Checkbox and radio buttons must be assigned a
nameprop when they are created, otherwise standard HTML treats them all as a single group. If a radio and checkbox component (or multiple) are created within the same page and they happen to have a value that's identical across both components, the pages will trigger incorrect behavior across both components. Adding a requirednameprop to both theCheckboxandRadiocomponent functions should fix this issue.Hey 👋 Can I fix this issue?
Hi @hparihar-07! I didn't realize that anyone was even looking at this repository. If you've got a suggestion, feel free to fork this and send a PR. I haven't really cleaned up the pages and I don't necessarily have the time to get you set up properly, but I've tried to document the setup process. Also, a fair warning that I can't give you access to the real data - you'll have to make and use your own AWS account with the correct DynamoDB tables set up if you'd like to test with data.
Let me know if you find a solution to this, or if you're not interested anymore (I know it's been a while) then I or @meraghon will take it over ourselves.