obsidian-plugin/bambuscontrol_obsidian-unicode-search
1
0
Fork 0
mirror of https://github.com/bambuscontrol/obsidian-unicode-search.git synced 2026-07-22 07:20:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
bambuscontrol_obsidian-unic.../DEVELOPMENT.md
Bambus Control e945278980 Multi-character codepoints don't trigger UCD download 
The Unicode `codepoint` can now be of any length in the normalized NFC form.
Fixes (again) #15.

See: e4746c699d
2025-09-27 13:23:23 +02:00

2.4 KiB
Raw Permalink Blame History

Unicode Search: Development

These are my notes on the development of the plugin.

Release: How To

  1. From the develop branch, create a release branch release/X.Y.Z
  2. Go to package.json and overwrite X.Y.Z-NEXT with new version throughout the whole project (double check if save data version needs to be updated)
  3. Update the package-lock file: npm install
  4. Export save data schema: npm run export-schema
  5. Run tests: npm run test
  6. Run build and test out the app: npm run build
  7. Commit as "Version X.Y.Z"
  8. Push, and fix if build fails, otherwise merge to the main branch
  9. Create a tag with the label X.Y.Z
  10. GitHub Actions will create a release
  11. Add release notes to the release
  12. Fast-forward the develop branch
  13. Go to package.json and overwrite X.Y.Z with next version X.Y.Z-NEXT throughout the whole project
  14. Update the package-lock file: npm install
  15. Commit as "Set version as X.Y.Z-NEXT" to the develop branch

Development Diary

27. September 2025

Unicode characters can be defined by multiple parts, which makes the string length in JavaScript larger than 1. I thought the "NFC" normalization limited the string to a length of 2, but that is not the case. The character U+FB2C has a length of 3, see issue #15. The "NFC" normalization is still applied, but I don't believe it will guarantee any maximum length of the string. Fixed in part thanks to https://dietcode.io/p/unicode-normalization/.

22. April 2025

The save data rework is kind-of done. Still, there is overlap between fetching and initializing data which I want to look at later.

23. December 2024

Before releasing the new feature, I have to fix the user save data implementation. Now it deletes their data when a new version of the plugin is loaded. So, it would forget the favorite characters after an update.

19. December 2024

This small plugin became a bit too elaborately written. I added the "favorite characters," and I'm almost done with it. It works alright, but adding new settings is tedious, so I'm thinking of adding Svelte as the next step (to make the UI modifications easier.)

Also, I want to simplify the code after, because I believe the codebase exploded for no good reason.