-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Help: Gatsby theme brain fails if any folder within the content folder #5
Comments
Updating to the latest version of Closing this. |
@aravindballa even after updating the deps, I'm facing an issue with the build.
any idea what's the issue is with? |
Can you help me reproduce this? I use Obsidian too, so I have |
Found the solution. It is happening because of the recent upgrade of It requires I think we should mention the same in this project ReadMe too so that users will not face the above issue. :) |
Ah yes. Will add that. Thanks :) |
Hi, @aravindballa thanks for the amazing project.
I'm using Obsidian as my note-taking tool to capture those ideas locally. The way I've set up Obsidian is to read everything from the
content
folder so that I can see those graphs and connections.Obsidian generates a
.obsidian
directory for config related things. Even though it's a hidden directory, I thinkgatsby-theme-brain
is trying to generate queries from the hidden directory. Because it's a directory and not a file, it's throwing an error saying that it is an illegal operation.I'm not sure if
gatsby-theme-andy
has any other config where could change/modify things a bit or if we should raise this issue ingatsby-theme-brain
orgatsby
.I have noticed that
notes.aravindballa.com
usesobsidian
too. As there is a mention of that in the.gitignore
.For now, when I'm doing any development... I'm deleting the config directory when I'm writing I'm putting in back. But it can become a boring chore too. I'm curious if others having any similar issues or found any ways to solve it. So posting it here in this repo.
The text was updated successfully, but these errors were encountered: