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
Following are the few features I want to implement before publishing the first version :
In the taskItem.tsx just put the taskItemBody div along with the {renderTaskBody()} obviously, outside the main checkbox div, so the body will take the whole width of the taskItemCard. Oh shit the subTasks and the body is connected inside that renderTaskBody(). I guess i have to create two rendering functions like this.
An option in settings to set the width of the columns, but there will be obviously a minimum width.
Issue : Extraction of Priority is not happening properly.
First try debugging, like putting the emoji just after the pipe symbol and then trying to detect it. ohh, try regEx, right now, i was trying to do it with simple comparing, but with regEx it might work, like match the pattern : ' ' or if that space before and after is not possible then simply '| ', that is the priority has to be always after the pipe symbol, no space then also fine.
If the detecting emoji is not happening at all, then, write a number instead of the emoji like : [1].
The real-Time scanning will be changed from toggle to drop down. It will have three options : Enable, Disable, Periodic.
If Enable, then as soon as the file is changed, it will be scanned and same time the tasks will be refreshed.
If Periodic, then i can also take time as well from user, at what time-interval does the user wants to check for file changes and scan them. I have decided not to keep this option, as it will simply reduce the image of this plugin. Instead I will mention in the setting that :
Now, If the RealTimeScanning is ON => As soon as the user looses focus from any editor/file, then that file will be scanned and the Board will be refreshed.
If Its OFF => The periodic functionality will be running anyways, the file will be scanned after sometime. But the board will not be scanned, the user will have to manually refresh the board using the Button.
If Disabled, modified files wont be scanned at all. The user will have to run the Re-Scan Vault Modal to get all the newly added tasks.
Here one optimization, read this value from the setting, and if disabled, then dont register that modify event, or i guess few other events wont be registered as well.
Improve the ReScanVault Modal to show the extracted tasks properly using MarkdownRenderer. And few other additions can be made to improve the look of the Modal.
Priority not detecting issue has been resolved, but the only problem is, the pipe symbol is must and the priority emoji should always be placed right after the pipe symbol, if there is any character in between, the priority wont be detected.
Since, big plugin, like Tasks use emoji to indicate priority hence i will have to use emoji only instead of number inside square brackets which dont make sense.
Following are the few features I want to implement before publishing the first version :
In the taskItem.tsx just put the taskItemBody div along with the
{renderTaskBody()}
obviously, outside the main checkbox div, so the body will take the whole width of the taskItemCard. Oh shit the subTasks and the body is connected inside that renderTaskBody(). I guess i have to create two rendering functions like this.An option in settings to set the width of the columns, but there will be obviously a minimum width.
Expand the tag feat to store multiple tags and also detect multiple tags. This has been explained further in feat : Adding Multiple tags to same task with custom colors #52 .
Issue : Extraction of Priority is not happening properly.
The real-Time scanning will be changed from toggle to drop down. It will have three options : Enable, Disable, Periodic.
Improve the ReScanVault Modal to show the extracted tasks properly using MarkdownRenderer. And few other additions can be made to improve the look of the Modal.
There are few small changes required in the AddOrEditTaskModal. See this issue : Few changes in the AddOrEditTaskModal #59
The text was updated successfully, but these errors were encountered: