-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Tickets to be considered for post-v5.1.23 #5231
Comments
#4558 - Add WebserverAPI for obtaining tags as JSON |
Another one we have postponed: |
#5252 - Edit: done |
#5192 - Consider dropping support for IE, and/or targeting a more recent version of Javascript. (Possibly for 5.2.x). |
#5275 - Feature tiddlywiki.files "searchSubdirectories" flag |
#2776 - navigate to the previous tiddler instead of the subsequent one |
#5302 - Add |
|
Thank you for this great tool. I have just started using it and I am absolutely amazed and delighted. I am a Chromebook user which has limited ability to encrypt files for cloud storage. Would be great if sensitive chunks of text inside tiddlers could be highlighted and then encrypted (similar to LockTheText which is a short JavaScript). |
#5279 - add server sent events |
@inmysocks - is there some change that could be made to native TW that would simplify/be a step towards federation? Perhaps something that you've solved for Bob but that you think would make sense in the core? |
add dynamic toolbar buttons + HowTo #5294 |
set initial tab size to 4 #5293 |
#3461 Add support for running external tasks on the server |
Still debugging the callbacks in the syncer/syncadapter relationship, but this is a targeted bug-fix that I needed to separate out: #5416 |
@Jermolene we should triage any tickets here that should be considered in the near term and close this issue. These are the tickets that stand out to me as worth a review: |
Thanks @saqimtiaz I've commented on each of the ones you've mentioned. There are probably others that would be worth picking up too, but I agree that this ticket should be closed. |
We've started deferring changes until after the imminent release of v5.1.23 (see #5130). This ticket is to act as a reminder for issues/PRs that we want to pick up for the next release.
The text was updated successfully, but these errors were encountered: