README.md update - extracted the details of Obsidian breaking changes into dedicated files, leaving only informative frames
This commit is contained in:
parent
89f032084d
commit
8ed1840f65
15
README.md
15
README.md
|
@ -1,15 +1,10 @@
|
|||
> | :exclamation: Breaking changes in Obsidian 1.6.0 (and newer) - update the plugin to 2.1.9 or newer|
|
||||
> |----------------------------------------------|
|
||||
> |[More details](README.notice.for.Obsidian.1.6.0.md)|
|
||||
|
||||
> | :exclamation: Breaking changes in Obsidian 1.5.4 (and newer) - update the plugin to 2.1.7 or newer|
|
||||
> |----------------------------------------------|
|
||||
>
|
||||
> Obsidian team introduced some breaking changes in File Explorer in a not-backward-compatible way starting from Obsidian 1.5.4.
|
||||
>
|
||||
> The **custom sort** plugin starting from release **2.1.7** was adjusted to work correctly with these breaking changes in Obsidian 1.5.4 and newer.
|
||||
> The plugin remains backward compatible, so you can safely update the plugin for Obsidian earlier that 1.5.4
|
||||
>
|
||||
> For more details of the observed misbehavior (of not updated plugin) you can go to [#131](https://github.com/SebastianMC/obsidian-custom-sort/issues/131) or [#135](https://github.com/SebastianMC/obsidian-custom-sort/issues/135) or [#139](https://github.com/SebastianMC/obsidian-custom-sort/issues/139)
|
||||
>
|
||||
> | :exclamation: Breaking changes in Obsidian 1.5.4 (and newer) - update the plugin to 2.1.7 or newer|
|
||||
> |----------------------------------------------|
|
||||
> |[More details](README.notice.for.Obsidian.1.5.4.md)|
|
||||
|
||||
---
|
||||
|
||||
|
|
|
@ -0,0 +1,11 @@
|
|||
> | :exclamation: Breaking changes in Obsidian 1.5.4 (and newer) - update the plugin to 2.1.7 or newer|
|
||||
> |----------------------------------------------|
|
||||
>
|
||||
> Obsidian team introduced some breaking changes in File Explorer in a not-backward-compatible way starting from Obsidian 1.5.4.
|
||||
>
|
||||
> The **custom sort** plugin starting from release **2.1.7** was adjusted to work correctly with these breaking changes in Obsidian 1.5.4 and newer.
|
||||
> The plugin remains backward compatible, so you can safely update the plugin for Obsidian earlier than 1.5.4
|
||||
>
|
||||
> For more details of the observed misbehavior (of not updated plugin) you can go to [#131](https://github.com/SebastianMC/obsidian-custom-sort/issues/131) or [#135](https://github.com/SebastianMC/obsidian-custom-sort/issues/135) or [#139](https://github.com/SebastianMC/obsidian-custom-sort/issues/139)
|
||||
>
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
> | :exclamation: Breaking changes in Obsidian 1.6.0 (and newer) - update the plugin to 2.1.9 or newer|
|
||||
> |----------------------------------------------|
|
||||
>
|
||||
> Obsidian team introduced some breaking changes in File Explorer sorting code in a not-backward-compatible way starting from Obsidian 1.6.0.
|
||||
>
|
||||
> The **custom sort** plugin starting from release **2.1.9** was adjusted to work correctly with these breaking changes in Obsidian 1.6.0 and newer.
|
||||
> The plugin remains backward compatible, so you can safely update the plugin for Obsidian earlier than 1.6.0
|
||||
>
|
||||
> For more details of the observed misbehavior (of not updated plugin) you can go to [#145](https://github.com/SebastianMC/obsidian-custom-sort/issues/145)
|
||||
|
Loading…
Reference in New Issue