Fix Slash Command lag, currently causing keystrokes to be missed
complete
T
Tom Ferguson
Quick use of the Slash Commands can often not work as intended due to a lag after the slash during which keystrokes are lost.
Log In
Waleed Elaghil
complete
T
Tarun Masani
Merged in a post:
Due date parsing too slow during task entry
D
Daniel Barrows
The task entry box has an unacceptable lag time when setting the due date. This is most pronounced in the web application, but even in the desktop application, there's a noticeable wait.
To replicate this problem:
- Login to Clickup.
- Click the "New Task" button.
- Type "Test task /d" then press <kbd>Enter</kbd>
- Type "4pm" [Enter]
- Type "/a" [Enter]
Often when I do this, at step 4 the [Enter] is ignored, and the due date field is instead "4pm/a". This is because Clickup is still processing the 4pm due date.
There are a few ways to fix this:
- Make the date parsing code faster.
- Make the date parse in the background once [Enter] is pressed, and show an error if it doesn't parse properly.
Option 2 is somewhat tricky as ClickUp doesn't show the due date, so any issues with date parsing would be hidden from the user.
D
Daniel Barrows
D
Daniel Barrows
Was about to file this myself. :)
The task entry box has an unacceptable lag time when setting the due date. This is most pronounced in the web application, but even in the desktop application, there's a noticeable wait.
To replicate this problem:
- Login to Clickup.
- Click the "New Task" button.
- Type "Test task /d" then press [Enter]
- Type "4pm" [Enter]
- Type "/a" [Enter]
Often when I do this, at step 4 the [Enter] is ignored, and the due date field is instead "4pm/a". This is because Clickup is still processing the 4pm due date.
There are a few ways to fix this:
- Make the date parsing code faster.
- Make the date parse in the background once [Enter] is pressed, and show an error if it doesn't parse properly. This is somewhat tricky as ClickUp doesn't show the due date, so any issues with date parsing would be hidden from the user.
- Developing a syntax to parse the entire line instead of just parsing specific fields, as proposed at https://feedback.clickup.com/feature-requests/p/parseable-task-entry-syntax If the task entry syntax is parseable as an entire line, then we don't need to wait for ClickUp to parse any specific portion before we can move on and keep typing the rest of the line.
Zeb
under review