-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Checkbox Group not updating v-model and not emitting change event #61
Comments
Thanks for the very well explained issue, could you update to v0.3.1 and see if the behavior is still the same? I'm not sure but I think 38a0ac8 fixed this 👍 |
Thanks, Rafael, for the swift reply. I hoped to reply as swiftly, but then my bosses dropped a bunch of beer on the conference table and I got... distracted. :) I've updated my package.json to include Results are the same as in my original post. :( I really think I've missed something here, but I can't figure out what it is. To edit a bit... When I add a v-model value to the first checkbox and then checking it, I see that its |
Found something more. In my original HTML, I wrapped each checkbox into a When I pull the <b-checkbox-group v-model="clients" @change="groupChange">
<b-checkbox custom-value="1" @change="checkChange">Item 1</b-checkbox>
<b-checkbox custom-value="2">Item 2</b-checkbox>
<b-checkbox custom-value="3">Item 3</b-checkbox>
<b-checkbox custom-value="4">Item 4</b-checkbox>
</b-checkbox-group> Removing the So it's functional, if we don't put the At least I understand what's happening now and why. Once I'm less distracted, I'll see if I can figure out how to fix it. |
After more testing, the wrapper Don't know why that happens and I don't know if you want to call it a bug or not, but I have what I need to make it work the way I want it to in my app at least. Cheers! |
Sorry for the delay, can you post the HTML before and after so I can try to find what's wrong? |
Hi Rafael, The original source is up there in my first post. The tag in question is the |
I'm closing this cause I couldn't reproduce, glad that you make it work 👍 |
* test(lib): update Modal spec - Introduces a new test case that tests a programmatically opened `Modal`. It tests if a DOM element with `modal` class is created after `open` and removed after `close`. - Splits the test case "emit events on close" so that each separated test case makes more sense: 1. "emit events on close but stay active": tests if "close" event is emitted when `close` is called. 2. "should be deactivated on close if programmatic": tests if `programmatic` `Modal` turns off `isActive` when `close` is called. No longer tests destruction of the component because `$destroy` is no longer available on Vue 3. A related test is moved to the new test case "should be able to be manually closed". - Updates other test cases for `Modal` so that they can work with `@vue/test-utils` V2: - Awaits `setProps` to make sure the subsequent tests verify the updated state. - Replaces `wrapper.name()` with `wrapper.vm.$options.name` because `wrapper.name` no longer exists in `@vue/test-utils` V2. - Replaces the test on `wrapper.isVueInstance()` with presence of `wrapper.vm` because `wrapper.isVueInstance` no longer exists in `@vue/test-utils` V2. - Renames `propsData` in the options for `shallowMount` to `props` because `propsData` might be deprecated in the future. - Refreshes the snapshot. The `transition` component becomes a stub to avoid potentially flaky snapshots. I did not see any problems in the updated snapshot. issue ntohq#1 * fix(lib): Modal with extra aria-modal - Fixes the issue that `Modal` had an extra `aria-modal` with `false` when `ariaModal` prop was `false`. The following comment pointed at the issue: - ntohq#61 (comment)
Overview of the problem
Buefy version: [^0.3.0]
Vuejs version: [^2.1.10]
OS/Browser: Windows, Chrome
Description
HTML:
script:
Steps to reproduce
Expected behavior
I expected the BCheckboxGroup's event to emit and its array values to change when I checked a checkbox inside the group. I expected the client array to have a value in it.
I suspect that this is my error, but the documentation seems to lack detail for this particular control (and others).
Actual behavior
See repro steps above.
The text was updated successfully, but these errors were encountered: