Not all properties present in types.json

[thoresson]

I have just installed Clipper for the first time. When I dragged’n’dropped types.json not all properties used in my vault did show up.

So I opened the file in VSCode, only to find out that a couple of the properties actually are missing in that file. What more info can I provide to sort this out?

Steps to reproduce

No idea. This is a vault I created from scratch Feb 2, 1:36pm. And I just noticed that types.json was last modified Feb 2, 1:53pm.

Have only had a few community plugins installed: Dataview, Minimal Theme Settings, QuickAdd, Style Settings, Templater, and Update time on edit. Most of them installed after the last modified timestamp for types.json – and all disabled when doing the screenshot above.

Did you follow the troubleshooting guide? [Y/N]

Yes. Tried with restricted mode. Problem persists.

Environment

SYSTEM INFO:
Obsidian version: v1.8.6
Installer version: v1.7.7
Operating system: Darwin Kernel Version 24.3.0: Thu Jan 2 20:24:16 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6000 24.3.0
Login status: logged in
Language: en
Catalyst license: insider
Insider build toggle: on
Live preview: on
Base theme: adapt to system
Community theme: Minimal v7.7.18
Snippets enabled: 1
Restricted mode: off
Plugins installed: 6
Plugins enabled: 6
1: Dataview v0.5.67
2: Minimal Theme Settings v8.1.1
3: QuickAdd v1.11.5
4: Style Settings v1.0.9
5: Templater v2.9.2
6: Update time on edit v2.4.0

RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

---

Additional information

[WhiteNoise]

Hello, there is a misunderstanding here.

types.json does not contain the type of all properties in your vault, just the ones where you have manually selected the type. The rest is guessed.

[thoresson]

Ah, I see! That also explains why the file is called types.json and not categories.json.

But then this in Clipper’s settings is a bit misleading? This sentence was what had me believe that I would get a list of all properties in my vault.

[WhiteNoise]

Yes, we are having an internal discussion on how to correct that.

[thoresson]

So the import of categories to Clipper is just a matter of convenience? I can just scratch both the defaults and what’s in types.json and configure the fields I want filled manually?