Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

conflict with obsidian formatting assistant #30

Closed
ksdavidc opened this issue Feb 1, 2023 · 3 comments
Closed

conflict with obsidian formatting assistant #30

ksdavidc opened this issue Feb 1, 2023 · 3 comments

Comments

@ksdavidc
Copy link

ksdavidc commented Feb 1, 2023

see Reocin/obsidian-markdown-formatting-assistant-plugin#65 (comment)
getting this message consistently in developer console

seems to be a conflict with markdown formatting assitant and will post problem there too...

turning off settings search eliminates error message

plugin:obsidian-markdown-formatting-assistant-plugin:5107 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'active')
    at eval (plugin:obsidian-markdown-formatting-assistant-plugin:5107:56)
    at e.addToggle (app.js:1:1135946)
    at SettingsTab.eval (plugin:obsidian-markdown-formatting-assistant-plugin:5106:22)
    at step (plugin:obsidian-markdown-formatting-assistant-plugin:79:23)
    at Object.eval [as next] (plugin:obsidian-markdown-formatting-assistant-plugin:60:53)
    at eval (plugin:obsidian-markdown-formatting-assistant-plugin:53:71)
    at new Promise (<anonymous>)
    at __awaiter (plugin:obsidian-markdown-formatting-assistant-plugin:49:12)
    at SettingsTab.display (plugin:obsidian-markdown-formatting-assistant-plugin:4893:16)
    at SettingsSearch.getTabResources (plugin:settings-search:170:15)
@valentine195
Copy link
Member

I can't recreate this and that plugin is unmaintained

@ksdavidc
Copy link
Author

Thank you for replying. Yes, I am sorry I couldn't give better specs. OFA may be unmaintained, but the developer is responding to me and might be amenable to fixing it if I can localize it.

I will have to better triage my plugins, but clearly these two aren't happy being in the same room, even it if is because of someone else in the room. If SA is on, and I turn OFA on, the error shows immediately in the console. And vice versa. No other errors in my console.

Admittedly, it is an extremely low priority bug that has no immediate significance, as both plugins seem to be working fine. It was more of a warning than anything else. Thank you again.

@valentine195
Copy link
Member

The error appears immediately because settings search renders plugin tabs to grab their data as soon as they are enabled. If there’s an error in the settings tab render that will show.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants