Skip to content

Commit f9c9c0b

Browse files
committed
Update of README.md and README.notice.for.Obsidian.1.7.2.md after the 3.1.0 release.
1 parent 8bd78ce commit f9c9c0b

File tree

2 files changed

+23
-8
lines changed

2 files changed

+23
-8
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
> | :exclamation: Breaking changes in Obsidian - always use the newest version of the plugin|
22
> |----------------------------------------------|
3-
> | - Obsidian 1.7.2 - no fixes for Obsidian breaking changes available --> [More details](README.notice.for.Obsidian.1.7.2.md)|
3+
> | - Obsidian 1.7.2 - update the plugin to 3.1.0 or newer --> [More details](README.notice.for.Obsidian.1.7.2.md)|
44
> | - Obsidian 1.6.3 - update the plugin to 2.1.11 or newer --> [More details](README.notice.for.Obsidian.1.6.3.md)|
55
> | - Obsidian 1.6.0 - update the plugin to 2.1.9 or newer --> [More details](README.notice.for.Obsidian.1.6.0.md)|
66
> | - Obsidian 1.5.4 - update the plugin to 2.1.7 or newer --> [More details](README.notice.for.Obsidian.1.5.4.md)|

README.notice.for.Obsidian.1.7.2.md

Lines changed: 22 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,31 @@
1-
> | :exclamation: Breaking changes in Obsidian 1.7.2 (and newer) - no fixes available|
1+
> | :exclamation: Breaking changes in Obsidian 1.7.2 - update the plugin to 3.1.0 or newer|
22
> |----------------------------------------------|
33
>
44
> Obsidian team introduced some more breaking changes in a not-backward-compatible way starting from Obsidian 1.7.2.
55
>
6-
> The observed issues are minor, no fixes available (a work in progress with unknown release date):
7-
> - the custom sort plugin is **unable to automatically apply the custom sort on start**
8-
> - prevalent on mobile
6+
> The observed issues were minor and related to initial automatic application of custom sorting.
7+
> 1. The custom sort plugin is **unable to automatically apply the custom sort on start**
8+
> - when the File Explorer is not visible on app start
99
> - for the _Lazy Plugin Loader_ plugin occurs by definition
10-
> - **workaround**: custom sorting has to be applied manually via the ribbon icon or the command 'sort on'
11-
> - the custom sort plugin **keeps showing the notifications** with each change to any note
12-
> - **workaround**: disable the notifications
10+
> - prevalent on mobile
11+
>
12+
> The release 3.1.0 fixed some of the scenarios by introducing a delay in initial auto-application
13+
> of custom sorting. The delay is by default set to 1 second and can be increased up to 30 seconds,
14+
> which can be needed for large vaults, large number of plugins or on mobile.
15+
>
16+
> At the same time, when the File Explorer is not visible on app start, the custom sorting can't be
17+
> applied automatically by definition: there is no instance of File Explorer. This is an unfortunate
18+
> side effect of the [deferred views](https://docs.obsidian.md/Plugins/Guides/Understanding+deferred+views)
19+
> introduced by Obsidian 1.7.2.
20+
> There is no cure for this scenario and the custom sorting has to be applied manually when the
21+
> File Explorer is eventually displayed. The simplest way is to click the ribbon icon (on desktop)
22+
> or use the command 'sort-on' on mobile.
23+
>
24+
> 2. The custom sort plugin **keeps showing the notifications** with each change to any note
25+
>
26+
> The release 3.1.0 fixed this fully
1327
>
28+
> ---
1429
> For more details of the observed misbehaviors you can go to:
1530
> - [#161: Find out how to automatically apply custom sort on app start / vault (re)load etc.](https://github.com/SebastianMC/obsidian-custom-sort/issues/161)
1631
> - [#162: \[bug\]\[minor\] Obsidian 1.7.2 breaking changes - when File Explorer is not displayed an attempt to apply custom sort fails with error](https://github.com/SebastianMC/obsidian-custom-sort/issues/162)

0 commit comments

Comments
 (0)