Open alex-willi opened 1 year ago
If a user will eventually be able to use them from the front end and they are working through postman, I would leave them in. As you build out an auth layer on the backend, some of that functionality might come back into play. That said, discuss it with your team and set up a new dev sprint timeline and see if it is immediately useful. If not clean it up.
For now, if your team had no plan to continue developing a resource (like comments for example) I would recommend creating a 'stub' or 'stash' in a dev-branch including the date for when it was last edited and then remove it from your main branch (source of truth).
If you have time, or a need for the code you can revisit the branch, but for now, it is isolate / deprecated. As a general rule, remove any code that is not essential to the current behavior of your app, especially when it won't be used in the near future.
I had some unused routes that i had planned on removing but because of time restraints I was unable to do so. With better planning they would have not been created in the first place.