docs(migration): Document unimplemented components #2319
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
commit: |
VividLemon
approved these changes
Oct 31, 2024
xvaara
added a commit
to xvaara/bootstrap-vue-next
that referenced
this pull request
Nov 8, 2024
* upstream/main: chore: release main (bootstrap-vue-next#2327) fix(BTable): dynamic slots not rendering fixes bootstrap-vue-next#2328 (bootstrap-vue-next#2329) feat(BTable): make it possible to style custom footers (bootstrap-vue-next#2314) chore: release main (bootstrap-vue-next#2323) fix(BFormGroup): fix layout problem when label-for is not used (bootstrap-vue-next#2321) chore: release main (bootstrap-vue-next#2320) feat(BPagination): add small screen support (bootstrap-vue-next#2308) docs(BFormTextarea): Update auto height section + refactor (bootstrap-vue-next#2313) docs(migration): Document unimplemented components (bootstrap-vue-next#2319) docs: fix tables are not being formatted (bootstrap-vue-next#2317)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the PR
As part of the parity pass, I went through and added notes for all not yet implemented or deprecated components. I errored towards marking things as NYI rather than deprecated. I don't think that any of the currently unimplemented components would necessarily block us from declaring a v1 (other than possibly the date/time related ones, which I believe @VividLemon is looking at now). Things like Jubotron, and Media, and PaginationNav can reasonably be worked around using straight bootstrap classes - if someone feels compelled to smooth things out by implementing BSVN components the wouldn't be breaking changes and could be added at any time, including after we declare the library production ready.
I'd be fine with drawing the line differently if @VividLemon or @xvaara has an opinion.
Small replication
N/A
PR checklist
What kind of change does this PR introduce? (check at least one)
fix(...)feat(...)fix(...)docs(...)The PR fulfills these requirements:
CHANGELOGis generated from these messages, and determines the next version type. Pull requests that do not follow conventional commits or do not have an override will be denied