tayainvestment.blogg.se

Tiddlydesktop security
Tiddlydesktop security











tiddlydesktop security
  1. #Tiddlydesktop security update
  2. #Tiddlydesktop security upgrade
  3. #Tiddlydesktop security code
tiddlydesktop security

fix paddings in tags chooser when there are no tags to display (c7b1d36).popups: improve paddings, remove border, add shadow (49e13fc, 9cdf984).tagged/tagging blocks on tiddler hover: hide borders (8669dab).messageArea: remove border, add shadow (c90334c).annotations: remove borders, adjust paddings, margins (7a9b4e1).

tiddlydesktop security

#Tiddlydesktop security code

code blocks: remove border, margin-left, fix code font size (f86eb3f, b8c0503).increase line height in editor (improve readability, 751d28d).fix ctrl+tab inserting tabs instead of browser tabs switch when chkInsertTabs is enabled (8fa859a).add href to prettyLinks to enable open in new tab and context menu (6a76b7b).Here's the changes summary for announcements: make core upgrading work in Timimi (without need to download, import & delete) or create a js analogue of Timimi and in MTS.migrate tests to Jest (already create a proof-of-concept approach), add autotests to CI.ideally, check commit prefixes with Husky too.finish the first wave of codestyle updating ( npm run lint should show no errors, but I'm updating files one by one since there are more issues and linting rules themselves are not finished), facilitate using of linter with something like Husky.try to substitute jQuery in repo with jQuery as a package dependency (for easy version bumps/experiments).

#Tiddlydesktop security upgrade

adapt core upgrade auto-check plugin into the core.deal with the "security" issues reported by github (those are in fact issues of build tools and not TW itself).contemporary core theme (not default styles update, but a theme as a tiddler/shadow).Things that I would like to add to the release very much, but better go to the next one:

#Tiddlydesktop security update

  • update docs on dev/contribute & release process (now dev branch is the main branch for development master is the release branch which may be renamed into main all PRs should go to dev commits should have prefixes like docs:, codestyle:, refactor:, fix:, infra:, feature:).
  • get RSS generation back by substituting Phantom.js (abandoned) with either Puppeteer or replicating the process without headless browser.
  • in fact, this causes also various ~formatting differences.
  • fix CI! Start with disabling RSS generation.
  • summarize the current release process, automate where possible (ideally: CI/CD on merge into master/main).
  • create SimplifiedUpgradingPlugin and clarify when it can be used and the overall upgrdaing without importing.
  • update site (index core, test.html, download, archive, may be content of index – what's new etc).
  • create GH release, attach built files → v2.9.3.
  • at least 4 users tested and provided feedback.
  • build core, announce and attach it, the plugin for autochecking upgrades, changes summary.
  • summarize changes and add thanks (at least some of them).
  • bump version (Version.js, package.json), tag commit.
  • for now, in a plugin (see comments) in 2.9.4, this will get into the core.
  • introduce auto checking updates availability (for now disabled by default).
  • This PR is created to encourage release of 2.9.3.













    Tiddlydesktop security