Merge branch 'main' into main

manifest.json

@@ -1,7 +1,7 @@
 {
     "id": "obsidian-livesync",
     "name": "Self-hosted LiveSync",
-    "version": "0.24.8",
+    "version": "0.24.10",
     "minAppVersion": "0.9.12",
     "description": "Community implementation of self-hosted livesync. Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
     "author": "vorotamoroz",

package.json

@@ -1,6 +1,6 @@
 {
     "name": "obsidian-livesync",
-    "version": "0.24.8",
+    "version": "0.24.10",
     "description": "Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
     "main": "main.js",
     "type": "module",
@@ -32,17 +32,17 @@
         "@types/pouchdb-mapreduce": "^6.1.10",
         "@types/pouchdb-replication": "^6.4.7",
         "@types/transform-pouch": "^1.0.6",
-        "@typescript-eslint/eslint-plugin": "^8.4.0",
+        "@typescript-eslint/eslint-plugin": "^8.23.0",
-        "@typescript-eslint/parser": "^8.4.0",
+        "@typescript-eslint/parser": "^8.23.0",
         "builtin-modules": "^4.0.0",
-        "esbuild": "0.23.1",
+        "esbuild": "0.24.2",
-        "esbuild-svelte": "^0.8.1",
+        "esbuild-svelte": "^0.9.0",
         "eslint": "^8.57.0",
         "eslint-config-airbnb-base": "^15.0.0",
-        "eslint-plugin-import": "^2.30.0",
+        "eslint-plugin-import": "^2.31.0",
         "events": "^3.3.0",
-        "obsidian": "^1.6.6",
+        "obsidian": "^1.7.2",
-        "postcss": "^8.4.45",
+        "postcss": "^8.5.1",
         "postcss-load-config": "^6.0.1",
         "pouchdb-adapter-http": "^9.0.0",
         "pouchdb-adapter-idb": "^9.0.0",
@@ -54,13 +54,13 @@
         "pouchdb-merge": "^9.0.0",
         "pouchdb-replication": "^9.0.0",
         "pouchdb-utils": "^9.0.0",
-        "prettier": "^3.3.3",
+        "prettier": "^3.4.2",
         "svelte": "^4.2.19",
         "svelte-preprocess": "^6.0.2",
-        "terser": "^5.31.6",
+        "terser": "^5.37.0",
         "transform-pouch": "^2.0.0",
-        "tslib": "^2.7.0",
+        "tslib": "^2.8.1",
-        "typescript": "^5.5.4"
+        "typescript": "^5.7.3"
     },
     "dependencies": {
         "@aws-sdk/client-s3": "^3.645.0",
@@ -70,10 +70,10 @@
         "diff-match-patch": "^1.0.5",
         "esbuild-plugin-inline-worker": "^0.1.1",
         "fflate": "^0.8.2",
-        "idb": "^8.0.0",
+        "idb": "^8.0.2",
         "minimatch": "^10.0.1",
         "octagonal-wheels": "^0.1.22",
-        "svelte-check": "^4.0.4",
+        "svelte-check": "^4.1.4",
         "xxhash-wasm-102": "npm:xxhash-wasm@^1.0.2"
     }
 }

src/modules/core/ModuleFileHandler.ts

@@ -205,13 +205,10 @@ export class ModuleFileHandler extends AbstractModule implements ICoreModule {
     ): Promise<boolean> {
         const file = typeof info === "string" ? this.storage.getFileStub(info) : info;
         const mode = file == null ? "create" : "modify";
-
+        const pathFromEntryInfo = typeof entryInfo === "string" ? entryInfo : getPath(entryInfo);
-        const docEntry =
+        const docEntry = await this.db.fetchEntryMeta(pathFromEntryInfo, undefined, true);
-            typeof entryInfo === "string"
-                ? await this.db.fetchEntryMeta(entryInfo, undefined, true)
-                : await this.db.fetchEntryMeta(entryInfo.path, undefined, true);
         if (!docEntry) {
-            this._log(`File ${entryInfo} is not exist on the database`, LOG_LEVEL_VERBOSE);
+            this._log(`File ${pathFromEntryInfo} is not exist on the database`, LOG_LEVEL_VERBOSE);
             return false;
         }
         const path = getPath(docEntry);
@@ -275,7 +272,7 @@ export class ModuleFileHandler extends AbstractModule implements ICoreModule {
             }
             // 2. if not, the content should be checked.
 
-            if (shouldApplied) {
+            if (!shouldApplied) {
                 const readFile = await this.readFileFromStub(existDoc);
                 if (await isDocContentSame(docData, readFile.body)) {
                     // The content is same. So, we do not need to update the file.

updates.md

@@ -14,6 +14,25 @@ Thank you, and I hope your troubles will be resolved!
 
 ---
 
+## 0.24.10
+
+### Fixed
+
+-   Fixed the issue which the filename is shown as `undefined`.
+-   Fixed the issue where files transferred at short intervals were not reflected.
+
+### Improved
+
+-   Add more translations: `ja-JP` (Japanese) by @kohki-shikata (Thank you so much)!
+
+### Internal
+
+-   Some files have been prettified.
+
+## 0.24.9
+
+Skipped.
+
 ## 0.24.8
 
 ### Fixed
@@ -76,118 +95,4 @@ Thank you, and I hope your troubles will be resolved!
 -   The status line and the log summary are now displayed more smoothly and efficiently.
     -   This improvement has also been applied to the logs displayed in the log pane.
 
-## 0.24.4
-
-### Fixed
-
--   Fixed so many inefficient and buggy modules inherited from the past.
-
-### Improved
-
--   Tasks are now executed in an efficient asynchronous library.
--   On-demand chunk fetching is now more efficient and keeps the interval between requests.
-    -   This will reduce the load on the server and the network.
-    -   And, safe for the Cloudant.
-
-## 0.24.3
-
-### Improved
-
--   Many messages have been improved for better understanding as thanks to the fine works of @Volkor3-16! Thank you so much!
--   Documentations also have been updated to reflect the changes in the messages.
--   Now the style of In-Editor Status has been solid for some Android devices.
-
-## 0.24.2
-
-### Rewritten
-
--   Hidden File Sync is now respects the file changes on the storage. Not simply comparing modified times.
-    -   This makes hidden file sync more robust and reliable.
-
-### Fixed
-
--   `Scan hidden files before replication` is now configurable again.
--   Some unexpected errors are now handled more gracefully.
--   Meaningless event passing during boot sequence is now prevented.
--   Error handling for non-existing files has been fixed.
--   Hidden files will not be batched to avoid the potential error.
-    -   This behaviour had been causing the error in the previous versions in specific situations.
--   The log which checking automatic conflict resolution is now in verbose level.
--   Replication log (skipping non-targetting files) shows the correct information.
--   The dialogue that asking enabling optional feature during `Rebuild Everything` now prevents to show the `overwrite` option.
-    -   The rebuilding device is the first, meaningless.
--   Files with different modified time but identical content are no longer processed repeatedly.
--   Some unexpected errors which caused after terminating plug-in are now avoided.
--
-
-### Improved
-
--   JSON files are now more transferred efficiently.
-    -   Now the JSON files are transferred in more fine chunks, which makes the transfer more efficient.
-
-## 0.24.1
-
-### Fixed
-
--   Vault History can show the correct information of match-or-not for each file and database even if it is a binary file.
--   `Sync settings via markdown` is now hidden during the setup wizard.
--   Verify and Fix will ignore the hidden files if the hidden file sync is disabled.
-
-#### New feature
-
--   Now we can fetch the tweaks from the remote database while the setting dialogue and wizard are processing.
-
-### Improved
-
--   More things are moved to the modules.
-    -   Includes the Main codebase. Now `main.ts` is almost stub.
--   EventHub is now more robust and typesafe.
-
-## 0.24.0
-
-### Improved
-
--   The welcome message is now more simple to encourage the use of the Setup-URI.
-    -   The secondary message is also simpler to guide users to Minimal Setup.
-        -   But Setup-URI will be recommended again, due to its importance.
-    -   These dialogues contain a link to the documentation which can be clicked.
--   The minimal setup is more minimal now. And, the setup is more user-friendly.
-    -   Now the Configuration of the remote database is checked more robustly, but we can ignore the warning and proceed with the setup.
--   Before we are asked about each feature, we are asked if we want to use optional features in the first place.
-    -   This is to prevent the user from being overwhelmed by the features.
-    -   And made it clear that it is not recommended for new users.
--   Many messages have been improved for better understanding.
-    -   Ridiculous messages have been (carefully) refined.
-    -   Dialogues are more informative and friendly.
-        -   A lot of messages have been mostly rewritten, leveraging Markdown.
-        -   Especially auto-closing dialogues are now explicitly labelled: `To stop the countdown, tap anywhere on the dialogue`.
--   Now if the is plugin configured to ignore some events, we will get a chance to fix it, in addition to the warning.
-    -   And why that has happened is also explained in the dialogue.
--   A note relating to device names has been added to Customisation Sync on the setting dialogue.
--   We can verify and resolve also the hidden files now.
-
-### Fixed
-
--   We can resolve the conflict of the JSON file correctly now.
--   Verifying files between the local database and storage is now working correctly.
--   While restarting the plug-in, the shown dialogues will be automatically closed to avoid unexpected behaviour.
--   Replicated documents that the local device has configured to ignore are now correctly ignored.
--   The chunks of the document on the local device during the first transfer will be created correctly.
-    -   And why we should create them is now explained in the dialogue.
--   If optional features have been enabled in the wizard, `Enable advanced features` will be toggled correctly.
-    The hidden file sync is now working correctly. - Now the deletion of hidden files is correctly synchronised.
--   Customisation Sync is now working correctly together with hidden file sync.
--   No longer database suffix is stored in the setting sharing markdown.
--   A fair number of bugs have been fixed.
-
-### Changed
-
--   Some default settings have been changed for an easier new user experience.
-    -   Preventing the meaningless migration of the settings.
-
-### Tiding
-
--   The codebase has been reorganised into clearly defined modules.
--   Commented-out codes have been gradually removed.
-
 Older notes are in [updates_old.md](https://github.com/vrtmrz/obsidian-livesync/blob/main/updates_old.md).

updates_old.md

@@ -1,8 +1,140 @@
+## 0.24.0
+
+I know that we have been waiting for a long time. It is finally released!
+
+Over the past three years since the inception of the plugin, various features have been implemented to address diverse user needs. This is truly honourable, and I am grateful for your years of support. However, this process has led to an increasingly disorganised codebase, with features becoming entangled. Consequently, this has led to a situation where bugs can go unnoticed and resolving one issue may inadvertently introduce another.
+
+In 0.24.0, I reorganised the previously jumbled main codebase into clearly defined modules. Although I had assumed that the total size of the code would not increase, I discovered that it has in fact increased. While the complexity is still considerable, the refactoring has improved the clarity of the code's structure. Additionally, while testing the release candidates, we still found many bugs to fix, which helped to make this plug-in robust and stable. Therefore, we are now ready to use the updated plug-in, and in addition to that, proceed to the next step.
+
+This is also the first step towards a fully-fledged-fancy LiveSync, not just a plug-in from Obsidian. Of course, it will still be a plug-in primarily and foremost, but this development marks a significant step towards the self-hosting concept.
+
+Finally, I would like to once again express my respect and gratitude to all of you. My gratitude extends to all of the dev testers! Your contributions have certainly made the plug-in robust and stable!
+
+Thank you, and I hope your troubles will be resolved!
+
+---
+
+## 0.24.4
+
+### Fixed
+
+-   Fixed so many inefficient and buggy modules inherited from the past.
+
+### Improved
+
+-   Tasks are now executed in an efficient asynchronous library.
+-   On-demand chunk fetching is now more efficient and keeps the interval between requests.
+    -   This will reduce the load on the server and the network.
+    -   And, safe for the Cloudant.
+
+## 0.24.3
+
+### Improved
+
+-   Many messages have been improved for better understanding as thanks to the fine works of @Volkor3-16! Thank you so much!
+-   Documentations also have been updated to reflect the changes in the messages.
+-   Now the style of In-Editor Status has been solid for some Android devices.
+
+## 0.24.2
+
+### Rewritten
+
+-   Hidden File Sync is now respects the file changes on the storage. Not simply comparing modified times.
+    -   This makes hidden file sync more robust and reliable.
+
+### Fixed
+
+-   `Scan hidden files before replication` is now configurable again.
+-   Some unexpected errors are now handled more gracefully.
+-   Meaningless event passing during boot sequence is now prevented.
+-   Error handling for non-existing files has been fixed.
+-   Hidden files will not be batched to avoid the potential error.
+    -   This behaviour had been causing the error in the previous versions in specific situations.
+-   The log which checking automatic conflict resolution is now in verbose level.
+-   Replication log (skipping non-targetting files) shows the correct information.
+-   The dialogue that asking enabling optional feature during `Rebuild Everything` now prevents to show the `overwrite` option.
+    -   The rebuilding device is the first, meaningless.
+-   Files with different modified time but identical content are no longer processed repeatedly.
+-   Some unexpected errors which caused after terminating plug-in are now avoided.
+-
+
+### Improved
+
+-   JSON files are now more transferred efficiently.
+    -   Now the JSON files are transferred in more fine chunks, which makes the transfer more efficient.
+
+## 0.24.1
+
+### Fixed
+
+-   Vault History can show the correct information of match-or-not for each file and database even if it is a binary file.
+-   `Sync settings via markdown` is now hidden during the setup wizard.
+-   Verify and Fix will ignore the hidden files if the hidden file sync is disabled.
+
+#### New feature
+
+-   Now we can fetch the tweaks from the remote database while the setting dialogue and wizard are processing.
+
+### Improved
+
+-   More things are moved to the modules.
+    -   Includes the Main codebase. Now `main.ts` is almost stub.
+-   EventHub is now more robust and typesafe.
+
+## 0.24.0
+
+### Improved
+
+-   The welcome message is now more simple to encourage the use of the Setup-URI.
+    -   The secondary message is also simpler to guide users to Minimal Setup.
+        -   But Setup-URI will be recommended again, due to its importance.
+    -   These dialogues contain a link to the documentation which can be clicked.
+-   The minimal setup is more minimal now. And, the setup is more user-friendly.
+    -   Now the Configuration of the remote database is checked more robustly, but we can ignore the warning and proceed with the setup.
+-   Before we are asked about each feature, we are asked if we want to use optional features in the first place.
+    -   This is to prevent the user from being overwhelmed by the features.
+    -   And made it clear that it is not recommended for new users.
+-   Many messages have been improved for better understanding.
+    -   Ridiculous messages have been (carefully) refined.
+    -   Dialogues are more informative and friendly.
+        -   A lot of messages have been mostly rewritten, leveraging Markdown.
+        -   Especially auto-closing dialogues are now explicitly labelled: `To stop the countdown, tap anywhere on the dialogue`.
+-   Now if the is plugin configured to ignore some events, we will get a chance to fix it, in addition to the warning.
+    -   And why that has happened is also explained in the dialogue.
+-   A note relating to device names has been added to Customisation Sync on the setting dialogue.
+-   We can verify and resolve also the hidden files now.
+
+### Fixed
+
+-   We can resolve the conflict of the JSON file correctly now.
+-   Verifying files between the local database and storage is now working correctly.
+-   While restarting the plug-in, the shown dialogues will be automatically closed to avoid unexpected behaviour.
+-   Replicated documents that the local device has configured to ignore are now correctly ignored.
+-   The chunks of the document on the local device during the first transfer will be created correctly.
+    -   And why we should create them is now explained in the dialogue.
+-   If optional features have been enabled in the wizard, `Enable advanced features` will be toggled correctly.
+    The hidden file sync is now working correctly. - Now the deletion of hidden files is correctly synchronised.
+-   Customisation Sync is now working correctly together with hidden file sync.
+-   No longer database suffix is stored in the setting sharing markdown.
+-   A fair number of bugs have been fixed.
+
+### Changed
+
+-   Some default settings have been changed for an easier new user experience.
+    -   Preventing the meaningless migration of the settings.
+
+### Tiding
+
+-   The codebase has been reorganised into clearly defined modules.
+-   Commented-out codes have been gradually removed.
+
 ### 0.23.0
+
 Incredibly new features!
 
 Now, we can use object storage (MinIO, S3, R2 or anything you like) for synchronising! Moreover, despite that, we can use all the features as if we were using CouchDB.
 Note: As this is a pretty experimental feature, hence we have some limitations.
+
 -   This is built on the append-only architecture. It will not shrink used storage if we do not perform a rebuild.
 -   A bit fragile. However, our version x.yy.0 is always so.
 -   When the first synchronisation, the entire history to date is transferred. For this reason, it is preferable to do this under the WiFi network.
@@ -18,6 +150,7 @@ I have a lot of respect for that plugin, even though it is sometimes treated as
 Hooray for open source, and generous licences, and the sharing of knowledge by experts.
 
 #### Version history
+
 -   0.23.23:
     -   Refined:
         -   Setting dialogue very slightly refined.
@@ -159,7 +292,7 @@ Hooray for open source, and generous licences, and the sharing of knowledge by e
         -   Some files have been separated into multiple files to make them more explicit in what they are responsible for.
 -   0.23.11:
     -   Fixed:
-    - Now we *surely* can set the device name and enable customised synchronisation.
+        -   Now we _surely_ can set the device name and enable customised synchronisation.
         -   Unnecessary dialogue update processes have been eliminated.
         -   Customisation sync no longer stores half-collected files.
         -   No longer hangs up when removing or renaming files with the `Sync on Save` toggle enabled.
@@ -235,6 +368,7 @@ Hooray for open source, and generous licences, and the sharing of knowledge by e
         -   Now Journal Sync works efficiently in download and parse, or pack and upload.
         -   Less server storage and faster packing/unpacking usage by the new chunk format.
 -   0.23.1
+
     -   Fixed:
         -   Now journal synchronisation considers untransferred each from sent and received.
         -   Journal sync now handles retrying.
@@ -248,8 +382,8 @@ Hooray for open source, and generous licences, and the sharing of knowledge by e
     -   New feature:
         -   Now we can use Object Storage.
 
-
 ### 0.22.0
+
 A few years passed since Self-hosted LiveSync was born, and our codebase had been very complicated. This could be patient now, but it should be a tremendous hurt.
 Therefore at v0.22.0, for future maintainability, I refined task scheduling logic totally.
 
@@ -261,6 +395,7 @@ Note: we got a very performance improvement.
 Note at 0.22.2: **Now, to rescue mobile devices, Maximum file size is set to 50 by default**. Please configure the limit as you need. If you do not want to limit the sizes, set zero manually, please.
 
 #### Version history
+
 -   0.22.19
     -   Fixed:
         -   No longer data corrupting due to false BASE64 detections.
@@ -302,9 +437,7 @@ Note at 0.22.2: **Now, to rescue mobile devices, Maximum file size is set to 50
         -   Many type-errors have been resolved.
         -   Obsolete file has been deleted.
 -   0.22.15:
-  - Improved:
+    -   Improved: - Faster start-up by removing too many logs which indicates normality - By streamlined scanning of customised synchronisation extra phases have been deleted.
-    - Faster start-up by removing too many logs which indicates normality
-    - By streamlined scanning of customised synchronisation extra phases have been deleted.
         ... To continue on to `updates_old.md`.
 -   0.22.14:
     -   New feature:
@@ -468,10 +601,10 @@ Note at 0.22.2: **Now, to rescue mobile devices, Maximum file size is set to 50
             -   🧩 Waiting chunks
             -   🔌 Working Customisation items (Configuration, snippets and plug-ins)
 
-
 ... To continue on to `updates_old.md`.
 
 ### 0.21.0
+
 The E2EE encryption V2 format has been reverted. That was probably the cause of the glitch.
 Instead, to maintain efficiency, files are treated with Blob until just before saving. Along with this, the old-fashioned encryption format has also been discontinued.
 There are both forward and backwards compatibilities, with recent versions. However, unfortunately, we lost compatibility with filesystem-livesync or some.
@@ -512,6 +645,7 @@ It will be addressed soon. Please be patient if you are using filesystem-livesyn
         -   WARNING: Since this version, the compatibilities with older Filesystem LiveSync have been lost.
 
 ## 0.20.0
+
 At 0.20.0, Self-hosted LiveSync has changed the binary file format and encrypting format, for efficient synchronisation.  
 The dialogue will be shown and asks us to decide whether to keep v1 or use v2. Once we have enabled v2, all subsequent edits will be saved in v2. Therefore, devices running 0.19 or below cannot understand this and they might say that decryption error. Please update all devices.  
 Then we will have an impressive performance.
@@ -526,7 +660,6 @@ This format change gives us the ability to detect some `marks` in the binary fil
 
 Now only a few chunks are transferred, even if we add a comment to the PDF or put new files into the ZIP archives.
 
-
 -   0.20.7
     -   Fixed
         -   To better replication, path obfuscation is now deterministic even if with E2EE.  
@@ -594,6 +727,7 @@ We can use the new feature with the same configuration. Only the menu on the com
 I hope you will give it a try.
 
 #### Minors
+
 -   0.19.1
     -   Fixed: Fixed hidden file handling on Linux
     -   Improved: Now customization sync works more smoothly.
@@ -771,10 +905,10 @@ I hope you will give it a try.
     -   Now, the hidden file scanning interval could be configured to 0.
     -   `Check database configuration` now points out that we do not have administrator permission.
 
-
 ### 0.18.0
 
 #### Now, paths of files in the database can now be obfuscated. (Experimental Feature)
+
 At before v0.18.0, Self-hosted LiveSync used the path of files, to detect and resolve conflicts. In naive. The ID of the document stored in the CouchDB was naturally the filename.
 However, it means a sort of lacking confidentiality. If the credentials of the database have been leaked, the attacker (or an innocent bystander) can read the path of files. So we could not use confidential things in the filename in some environments.
 Since v0.18.0, they can be obfuscated. so it is no longer possible to decipher the path from the ID. Instead of that, it costs a bit CPU load than before, and the data structure has been changed a bit.
@@ -783,6 +917,7 @@ We can configure the `Path Obfuscation` in the `Remote database configuration` p
 Note: **When changing this configuration, we need to rebuild both of the local and the remote databases**.
 
 #### Minors
+
 -   0.18.1
     -   Fixed:
         -   Some messages are fixed (Typo)
@@ -800,6 +935,7 @@ Note: **When changing this configuration, we need to rebuild both of the local a
         -   Case-sensitive renaming now works fine.
             Revoked the logic which was made at #130, however, looks fine now.
 -   0.18.5
+
     -   Improved:
         -   Actions for maintaining databases moved to the `🎛️Maintain databases`.
         -   Clean-up of unreferenced chunks has been implemented on an **experimental**.
@@ -815,10 +951,12 @@ Note: **When changing this configuration, we need to rebuild both of the local a
             -   It let us free from conflict resolution on initial synchronising.
 
 ### 0.17.0
+
 -   0.17.0 has no surfaced changes but the design of saving chunks has been changed. They have compatibility but changing files after upgrading makes different chunks than before 0.16.x.
     Please rebuild databases once if you have been worried about storage usage.
 
     -   Improved:
+
         -   Splitting markdown
         -   Saving chunks
 
@@ -828,19 +966,23 @@ Note: **When changing this configuration, we need to rebuild both of the local a
 #### Minors
 
 -   0.17.1
+
     -   Fixed: Now we can verify and repair the database.
     -   Refactored inside.
 
 -   0.17.2
+
     -   New feature
         -   We can merge conflicted documents automatically if sensible.
     -   Fixed
         -   Writing to the storage will be pended while they have conflicts after replication.
 
 -   0.17.3
+
     -   Now we supported canvas! And conflicted JSON files are also synchronised with merging its content if they are obvious.
 
 -   0.17.4
+
     -   Canvases are now treated as a sort of plain text file. now we transfer only the metadata and chunks that have differences.
 
 -   0.17.5 Now `read chunks online` had been fixed, and a new feature: `Use dynamic iteration count` to reduce the load on encryption/decryption.
@@ -992,6 +1134,7 @@ Note: **When changing this configuration, we need to rebuild both of the local a
     -   Refactored again: Internal file sync, plug-in sync and Set up URI have been moved into each file.
 
 ### 0.16.0
+
 -   Now hidden files need not be scanned. Changes will be detected automatically.
     -   If you want it to back to its previous behaviour, please disable `Monitor changes to internal files`.
     -   Due to using an internal API, this feature may become unusable with a major update. If this happens, please disable this once.
@@ -1026,12 +1169,14 @@ Note:
 Before 0.16.5, LiveSync had some issues making chunks. In this case, synchronisation had became been always failing after a corrupted one should be made. After 0.16.6, the corrupted chunk is automatically detected. Sorry for troubling you but please do `rebuild everything` when this plug-in notified so.
 
 ### 0.15.0
+
 -   Outdated configuration items have been removed.
 -   Setup wizard has been implemented!
 
 I appreciate for reviewing and giving me advice @Pouhon158!
 
 #### Minors
+
 -   0.15.1 Missed the stylesheet.
 -   0.15.2 The wizard has been improved and documented!
 -   0.15.3 Fixed the issue about locking/unlocking remote database while rebuilding in the wizard.
@@ -1046,6 +1191,7 @@ I appreciate for reviewing and giving me advice @Pouhon158!
     -   Auto applying of batch save will be processed earlier than before.
 
 ### 0.14.1
+
 -   The target selecting filter was implemented.
     Now we can set what files are synchronised by regular expression.
 -   We can configure the size of chunks.
@@ -1057,11 +1203,13 @@ I appreciate for reviewing and giving me advice @Pouhon158!
 -   Use local chunks in preference to remote them if present,
 
 #### Recommended configuration for Self-hosted CouchDB
+
 -   Set chunk size to around 100 to 250 (10MB - 25MB per chunk)
-- *Set batch size to 100 and batch limit to 20 (0.14.2)*
+-   _Set batch size to 100 and batch limit to 20 (0.14.2)_
 -   Be sure to `Read chunks online` checked.
 
 #### Minors
+
 -   0.14.2 Fixed issue about retrieving files if synchronisation has been interrupted or failed
 -   0.14.3 New test items have been added to `Check database configuration`.
 -   0.14.4 Fixed issue of importing configurations.
@@ -1080,6 +1228,7 @@ I appreciate for reviewing and giving me advice @Pouhon158!
 -   Update information became to be shown on the major upgrade.
 
 #### Minors
+
 -   0.13.1 Fixed on conflict resolution.
 -   0.13.2 Fixed file deletion failures.
 -   0.13.4