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
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!).
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)
UPDATE by @samreid, currently at:
The text was updated successfully, but these errors were encountered: