-
Notifications
You must be signed in to change notification settings - Fork 43
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
Type Mismatch on "banner_header" key #121
Comments
That's true actually. I forgot about the upcoming database changes would probably require properties to be consistent with their types. For the time being, I think using an empty string could also work to trigger the automatic filename |
Yea that sounds like a better solution, great this will be fixed b4 it's out of beta! |
All good to go in https://github.com/noatpad/obsidian-banners/releases/tag/2.0.2-beta! An empty (or rather |
The automatic header filename uses a boolean, where as the custom name uses a string, could cause incompatibilities with the upcoming obsidian databases & gives you a
ugly(kinda nice looking) warning symbol depending on whether your first banner header was a filename or a custom one.One solution could be to just use a word like "filename" to trigger the automatic header, could allow the user to change that in setting too
The text was updated successfully, but these errors were encountered: