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
It seems the changes in PR #3384 break some sidebars, at least in my case:
Here's what the sidebars should look like
And here's what a method/property/constructor page actually looks like:
Clearly the ProtoSocket-class-sidebar.html file exists and loads fine, but I noticed the constructor/method/property pages don't even request it!
Here are the network requests for the ProtoSocket page:
And here are the requests for the init method:
Here's the code for the main-content on the ProtoSocket page:
When I edit the HTML to put the sidebar on the right as well, it loads... but only on the right side. My repository is here, feel free to ask for more info.
Levi-Lesches
changed the title
@srawlins I'm really impressed by the sidebars PR #3384, but it broke my docs (in version 6.3.0) :(
Left sidebar not showing on some docs
Jul 20, 2023
Not sure what changed but this is working now. The output above was generated with dart pub global run dartdoc and some more options, while the below was generated with dart doc, but I didn't upgrade the version since making this issue.
It seems the changes in PR #3384 break some sidebars, at least in my case:


Here's what the sidebars should look like
And here's what a method/property/constructor page actually looks like:
Clearly the


ProtoSocket-class-sidebar.html
file exists and loads fine, but I noticed the constructor/method/property pages don't even request it!Here are the network requests for the
ProtoSocket
page:And here are the requests for the
init
method:Here's the code for the
main-content
on theProtoSocket
page:And here's the code for the
init
method:When I edit the HTML to put the sidebar on the right as well, it loads... but only on the right side. My repository is here, feel free to ask for more info.
Originally posted by @Levi-Lesches in #3079 (comment)
The text was updated successfully, but these errors were encountered: