-
Notifications
You must be signed in to change notification settings - Fork 2
Open
2 / 72 of 7 issues completedLabels
WIPIt's being worked onIt's being worked onbalancethe pain is too much (or too little)the pain is too much (or too little)good first issueGood for newcomersGood for newcomershas pull requesthelp wantedExtra attention is neededExtra attention is neededplaceholderThis issue is not an issueThis issue is not an issue
Description
What is the problem?
This tracking issue exists in order to resolve the following three common complaints when navigating through recipe chains in pY:
"Why does this recipe exist? I would never use this."
or
"This recipe is too strong, I would never use the alternatives"
or
"This TURD upgrade is too weak. Who would choose this?"
Please list the following:
- What is the internal name of the recipe/TURD path? You can find this by hovering the recipe and pressing
ctrl+shift+f - Why do you feel that it is underpowered/overpowered?
- What suggestion would you make to fix the issue?
Reports are intended to be concise. If you find yourself writing an essay, it may be more useful to open a dedicated bug ticket.
Sub-issues
Metadata
Metadata
Assignees
Labels
WIPIt's being worked onIt's being worked onbalancethe pain is too much (or too little)the pain is too much (or too little)good first issueGood for newcomersGood for newcomershas pull requesthelp wantedExtra attention is neededExtra attention is neededplaceholderThis issue is not an issueThis issue is not an issue
Type
Projects
Status
Has PR