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
We could convert examples to be a test-like project instead of adding a new one. Alternatively, could say "Hey! The examples were useful back when we had no docs, and are pretty thin now. What if we just made sure everything was documented or a recipe, if deserving, and remove that project". (Then again, if we added recipes to the "Examples*" project(s) (under "sample", which I never noticed before, we could still thin them out later if we wanted.)
Based on my actions, I slightly preferred a new [recipes] project (and removing the old ones)
So, once we have runnable recipes that are included in the docs via snippets, we should examine the examples projects and see if they still provide value. For each example, we should be able to
find it in the docs, or
add it to the docs (as a recipe or not)
and then remove it!
The text was updated successfully, but these errors were encountered:
Inspired by a comment I made in PR 1915.
So, once we have runnable recipes that are included in the docs via snippets, we should examine the examples projects and see if they still provide value. For each example, we should be able to
and then remove it!
The text was updated successfully, but these errors were encountered: