-
Notifications
You must be signed in to change notification settings - Fork 120
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
Fix / remove warnings in Masonry documentation #449
Labels
documentation
Improvements or additions to documentation
masonry
Issues relating to the Masonry widget layer
Comments
waywardmonkeys
added
documentation
Improvements or additions to documentation
masonry
Issues relating to the Masonry widget layer
labels
Jul 25, 2024
This is even worse with |
waywardmonkeys
added a commit
to waywardmonkeys/xilem
that referenced
this issue
Aug 2, 2024
This is a start on linebender#449.
This was referenced Aug 2, 2024
waywardmonkeys
added a commit
to waywardmonkeys/xilem
that referenced
this issue
Aug 2, 2024
This is a start on linebender#449.
github-merge-queue bot
pushed a commit
that referenced
this issue
Aug 2, 2024
This is a start on #449.
waywardmonkeys
added a commit
to waywardmonkeys/xilem
that referenced
this issue
Aug 25, 2024
This is work towards linebender#449.
waywardmonkeys
added a commit
to waywardmonkeys/xilem
that referenced
this issue
Aug 25, 2024
This is work towards linebender#449.
github-merge-queue bot
pushed a commit
that referenced
this issue
Aug 25, 2024
This is work towards #449.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
masonry
Issues relating to the Masonry widget layer
Separate from #389, the warnings when running
cargo doc -p masonry
need to be fixed.Most of them are about things that no longer exist within masonry or have perhaps changed names, so it should be a pretty quick pass.
This is blocking re-enabling denying warnings within CI for xilem documentation and has already led to an issue in that regard with a broken link making its way into there.
The text was updated successfully, but these errors were encountered: