Skip to content

On load unsafe registry

Falcion edited this page Oct 22, 2024 · 1 revision

On-load unsafe registry is a sub-variation of the default OLR system ("on-load registry"), which differs not in handling files, but in handling extensions of the given files by the create event of the Obsidian Vault. Instead of just reading the entire "post-first dot" part of the file as the extension (excluding the "filename"), it splits the "post-first dot" part into a sequence of extensions from which the "total extension" is derived.

Important

On-load unsafe registry (OLUR) is mutually exclusive with the default OLR system, meaning you can only enable one of them at a time through the plugin's UI. If you require both modes enabled, you can try enabling them through the data.json settings until the next setup of the plugin.

This mode can be helpful if your Vault contains "consecutive" files, meaning files with inherited extensions one by one from other data, example types, etc. Here is a logical example of OLUR working output:

# Input (filename):
file.data.json.log0

# Transforming file
Name: 'file'
Extension: 'data.json.log0'

# Intermediate output (if "case-insensitive mode" enabled):
['data', 'json', 'log0']

# Output (if "case-insensitive mode" enabled):
['datA', 'daTA' ..., 'jSon', 'jsON' ...]

Warning

Keep in mind, in the OLUR system, if "case-insensitive extensions" is enabled, every extension will be registered through an O ( n 2 n ) function, generating variants of extensions.

More about it: "Case-insensitive extensions mode"

Clone this wiki locally