Closed AnnMarieW closed 3 years ago
Amazing! Thanks so much for taking the time to go through this list @AnnMarieW! I haven't read them all super carefully yet, but it looks like these are all great suggestions.
Once we get the #646 finished up and merged into v1
branch, I would be very happy for us to start working through this list.
@AnnMarieW - I've been working through some of the docs snippets and fixing components where I can. I think over in PR #653 I've now got all the layouts working, but having some issues with a couple of pesky javascript and callback ones (if you wanted to take a look, feel free to). Happy to start working through some of these too.
Also noticed a couple of other things in the docs (they may be things that have been broken in #646 / #653, but including here so it's all in one place):
Hi @glsdown Thanks for your comments -- I'll keep an eye on #653 and #646 and update the progress here too.
Many of the suggestions for examples to add are low priority. I know that any additions come with the overhead of maintaining them in the long term, not only in Python, but in Julia and R as well. They should probably be ranked for the ones that would add the most value. I have marked the items with bugs and 2 examples that I think have a higher priority with a :arrow_up_small:
The Dropdown menu bugs are noted here already, but I the first Tooltip example and Navbar collapse seems to work for me. It's just the Dropdown menu inside the collapsed Navbar that doesn't work. Do you think it's just different versions?
btw, I :heart_eyes: the Accordion, Offcanvas, Pagnation, and Breadcrumb components you added. I can't wait for V1 to be live!
Thanks! I've had a lot of help with them though.
Unfortunately, none of them appear to work for me on the react-bootstrap branch #646 , so it's probably something @tcbegley or I have broken in the move over to react-bootstrap (unless that's the one you are working on, in which case I have no idea why it's not working for me). With the drop downs, all of them are really temperamental. Some of them work when you click on them, some of them bring up a drop down halfway across the screen, and some of them just don't display anything. The same drop down will exhibit all 3 behaviours too...
I'll take a look at it this evening, and see where it has been introduced.
@AnnMarieW I've made some of the changes above (now ticked) and they should now all be merged into v1 branch.
@tcbegley has said not to do the following though:
In the sidebar...
He thinks that having the sidebar as the component name works at the moment rather than copying the bootstrap style.
Also he said to leave for now until it's clearer what Dash are doing:
Additionally outstanding from the work I was doing on updating and making sure tests were run are:
carousel
- this auto advances with R and Julia. I think setting interval=None
is the thing that stops it advancing in python, but the equivalents in R (NULL
) and julia (nothing
) don't do the same thing (also tried with 0, and that didn't work either).modal
- R/JL callbacks not working for size but I'm unsure why as the python one does, and I can't see there are any functional differencesoffcanvas
- issues as using the version of bootstrap that has the backdrop in front of the offcanvas so all tests will fail - need to get this fixed by react-bootstrap (appears to be a closed PR recently so shouldn't be long now)popover
- It doesn't appear that the component ID is being passed to the element on the page which is why the tests themselves are failing here, although even if the tests were working, it seems to respond differently to bools in JL as doesn't react to 0 and 1, but does to explicit true/false, however, can't narrow down what is causing the callbacks to fail.docs/components_page/components/main.md
Great - I made updates to the checklist.
Good point regarding not changing the names on the sidebar - it makes more sense to match the component name. I'm still not sure whether it's worthwhile adding more new examples, but they can stay on the list as low priority suggestions.
One to add on the list above:
Another item to add to the list above:
class_name
in their components, we ought to change the html ones back to className
. This does depend on the note in the original bit though about delaying moving all components back to className
, and how quickly this is pushed out over.
It's awesome to see the progress on the Bootstrap 5 support - there are so many cool new features. :confetti_ball:
Here is a list of suggested changes and additions to the documentation. Perhaps we can use this to track all pre-release issues in the docs. This looks like a long list, but most of the items will be easy to fix. I'm happy to get started on a PR for any of the changes you approve.
Home page
Themes Page
Left Nav menu
Quickstart
Overall
className
andclass_name
. (Fixed in v1)<a>
and<button>
elements. We are still showing a hover effect inBadge
. Should this be changed in the component?~ Not changing this now. Will reconsider if people start complaining.Output, Input State
in snippets~ Worth keeping as is, as it maintains backwards compatibility, and doesn't provide that many advantages over the current approachComponent Landing Page
Icons Page
Accordion
Alerts
Badge
class_name
to"bg-secondary"
(Fixed in #659 )badge-*
color classes and now you need to set background color and text color independently. There is now atext_color
prop. Should we demo this new prop instead of addingtext-primary
to theclass_name
? (Fixed in #659 )class_name
in the "bg-light" example. (Fixed in #659 )Breadcrumb
Buttons and Button Groups
Add ToggleButton and ToggleButtonGroup components from react-bootstrap. Add "Toggle states" example, and remove the "RadioItems as ButtonGroup" example.(Save for a future release)download
prop. (Fixed in #660 )Dropdown
insideButtonGroup
isn't formatted correctly (Fixed in #662 )Card
Carousel
Collapse
Dropdown Menu
Divider=True
does not show a divider. (Fixed in #662 )Fade
Input
FormGroup
(Fixed in #674 )InputGroup
Jumbotron
Layout
ListGroup
Modal
loading_state
being passed toModalHeader
andModalTitle
. Should be omitted. (Fixed in #666 )Nav
active
property inNavItem
, but is there a workaround for this? react-bootstrap does not have a prop foractive
inNavItem
(Clarified in #675 )NavBar
Offcanvas
Pagination
Popover
Progress
app.long_callback
? (Might be complicated as docs are reasonably high traffic and lots of people running the example could swamp the docs server. Maybe a non-running example / link toexamples/
)~ Not right now as we don't want to deploy Redis backend for the docs, too much complexity for marginal value.Spinners
Tabs
card=True
is no longer required? If so the text in "Tabs in cards" example should be updated. Plus, should it be removed from here inTabs.js
?Table
Toast
Tooltips