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
Issue 10441 ToDo Improvement #13979
Issue 10441 ToDo Improvement #13979
Conversation
@@ -3,14 +3,14 @@ | |||
<li> | |||
<button class="task" data-key="{{ key }}"> | |||
</button> | |||
<span class="task">{{ task }}</span> | |||
<span class="task"><b>{{ task }}</b></span> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We generally use the modern strong
and em
tags, not b/i.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I'll change that. Should I add a new commit and push or squash all the commits abd push? As the documentation reads that solving of a particular issue should belong to a single commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@majordwarf You should add it to the 1st commit. You can do it in a number of ways. Rebasing or git commit --amend
can both help with that.
@vinitS101 Yeah, I've mentioned that in the PR itself as an issue I'm facing. Can you guide me if you know what is causing that? |
Check
You need to do something similar for |
The user can pass description along with the task name by splitting the input string with hyphen. Eg: Task Title - Task Description todo_list: Add index numbers to task.
@vinitS101 @timabbott I guess everything is fixed now. 🤔 |
LGTM. |
Merged! I am not super familiar with the todo widget, so I've never noticed its strange numbering issues. (We generally don't want zero-based indexes for user-facing things, and the indexes should sort.) But I think those quirks preceded your change. Sorry it look so long to review this! Thanks for working on it. |
Partially fixes: #10441
Testing Plan:
GIFs or Screenshots:
Issue