Open Jermolene opened 2 weeks ago
Confirmed: Jermolene has already signed the Contributor License Agreement (see contributing.md)
Name | Link |
---|---|
Latest commit | 55cf0b29657e3560526534f172d5de684f048ffe |
Latest deploy log | https://app.netlify.com/sites/tiddlywiki-previews/deploys/672ceaf559d3f800081fab88 |
Deploy Preview | https://deploy-preview-8730--tiddlywiki-previews.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
When updating the flexoki palette, I found that the tag won't display properly unless index background
, foreground
and tag-background
's value is hardcoded. So the wikify operator should be used in the tag macro.
But we had better not use it at present since tag pill is often used in UI, which may cause performance issues.
When updating the flexoki palette, I found that the tag won't display properly unless index
background
,foreground
andtag-background
's value is hardcoded. So the wikify operator should be used in the tag macro.
Ouch. I suspect that the compiled palette idea under investigation in #8702 will resolve a number of issues like this, and ultimately should allow us to significantly improve the stylesheet refresh performance.
This PR adds a "wikify" operator that has the same functionality as the wikify widget. I regard this as quite controversial because while it unlocks some important capabilities, it also suffers from performance issues and invites users to adopt patterns that can be dangerous:
<$list>
widget to generate a set of numbers instead of the[range[]]
operator. Besides being horribly inefficient, there are pitfalls with unexpected wikificationThis PR is cherry picked from #8702; I plan to refactor the work there to not require the wikify operator because of the performance issues.
The question now is what are the use cases for the wikify operator, and are there any other ways to accomplish those use cases?