ci: check for unused snippets - #108
Conversation
8ddcccb to
3f296f5
Compare
3f296f5 to
3b549bd
Compare
3b549bd to
61aa854
Compare
86667
left a comment
There was a problem hiding this comment.
Im not convinced that this is necessary - what is the harm in having some unused snippets really?
Also, a linter would likely be an easier way to identify unused code.
This feels like polish which will only get in the way whilst the repo is in its current development stages
The goal is to protect us from unnecessary maintenance work.
I don't see how you would achieve the same thing with a linter
How would it get in our way? You mean if you created a snippet, but don't want to reference it in the docs yet? Then you could just exclude it, right? At least you are conscious that there is 'dead code' or rather 'dead docs'. |
|
Blocked: Won't be merged until we're done with a major restructuring of the docs. |
Fails snippet CI when an anchored source snippet is unused.
Temporarily excludes React Native snippets until September 11, 2026 because the React Native library is not yet ready. The snippets will be reintroduced once the React Native library is on SDK version 0.10.0 as well.