You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
9
+
10
+
### Steps to reproduce the bug
11
+
12
+
1. Go to [...]
13
+
2. Click on [...]
14
+
3. Scroll down to [...]
15
+
4. See error
16
+
17
+
### Expected behavior
18
+
19
+
A clear and concise description of what you expected to happen.
20
+
21
+
### Versions
22
+
23
+
**Libraries:**
24
+
25
+
- BootstrapVue: 2.#.#
26
+
- Bootstrap: 4.#.#
27
+
- Vue: 2.#.#
28
+
29
+
**Environment:**
30
+
31
+
- Device: [e.g. Mac or iPhone X]
32
+
- OS: [e.g. macOS Mojave or iOS 12]
33
+
- Browser: [e.g. Chrome]
34
+
- Version: [e.g. 70]
35
+
36
+
### Demo link
37
+
38
+
If applicable, add a minimal demo link to help explain your problem. Some options for that are [CodePen](https://codepen.io/), [CodeSandbox](https://codesandbox.io/), [JS Bin](https://jsbin.com/) or [JSFiddle](https://jsfiddle.net/).
39
+
40
+
You can also export markup from the [Online Playground](https://bootstrap-vue.js.org/play) to _CodePen_, _CodeSandbox_ or _JSFiddle_.
"fix(alert): not alerting during SSR render", "docs(badge): Updated pill examples, fix typos",
38
-
"chore: fix typo in docs", etc). **This is very important, as the `CHANGELOG` is generated
39
-
from these messages.**
26
+
-[ ] When resolving a specific issue, it's referenced in the PR's title (i.e. `[...] (fixes #xxx[,#xxx])`, where "xxx" is the issue number)
27
+
-[ ] It should address only one issue or feature. If adding multiple features or fixing a bug and adding a new feature, break them into separate PRs if at all possible.
28
+
-[ ] The title should follow the [**Conventional Commits**](https://www.conventionalcommits.org/) naming convention (i.e. `fix(alert): not alerting during SSR render`, `docs(badge): update pill examples, fix typos`, `chore: fix typo in README`, etc). **This is very important, as the `CHANGELOG` is generated from these messages.**
40
29
41
30
**If new features/enhancement/fixes are added or changed:**
42
31
43
-
-[ ] Includes documentation updates (including updating the component's `package.json` for slot and
44
-
event changes)
32
+
-[ ] Includes documentation updates (including updating the component's `package.json` for slot and event changes)
45
33
-[ ] New/updated tests are included and passing (if required)
46
34
-[ ] Existing test suites are passing
47
35
-[ ] The changes have not impacted the functionality of other components or directives
48
-
-[ ] ARIA Accessibility has been taken into consideration (does it affect screen reader users or
49
-
keyboard only users? clickable items should be in the tab index, etc)
36
+
-[ ] ARIA Accessibility has been taken into consideration (Does it affect screen reader users or keyboard only users? Clickable items should be in the tab index, etc.)
50
37
51
38
**If adding a new feature, or changing the functionality of an existing feature, the PR's
52
39
description above includes:**
53
40
54
-
-[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a
55
-
suggestion issue first and wait for approval before working on it)
41
+
-[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)
0 commit comments