-
Notifications
You must be signed in to change notification settings - Fork 6
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
TODOs in this repo should point to useful github issues #102
Comments
zepumph
referenced
this issue
Sep 15, 2023
this is a duplicate of #76. Although it now seems like there are 94 instead of 70. Closing as a duplicate. |
zepumph
added a commit
that referenced
this issue
Oct 30, 2023
Updated todos pointing to this issue so it doesn't reopen tonight. |
Ope thanks for that. I believe I did a couple of others that I should hit as well. |
You did this everywhere. What a gem. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PhET has a policy that TODOs in production code are tied to a github issue to help in scheduling their work. This policy was created after many TODOs were created without a corresponding github issue associated with them in this repo. Never the less, this code is still production code, and TODOs should adhere to this philosophy. I'll mark TODOs in this repo to this issue now, but this should NOT be a catch all, work should be done to handle, triage, schedule and fix the work outlined by the TODOs in this repo (it is production code!).
(see work done in phetsims/tasks#1129 also)
The text was updated successfully, but these errors were encountered: