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

[Bug]: List properties with links do not get interpreted as relations and inline fields used regardless of setting #998

Open
2 tasks done
brad-decker opened this issue Nov 8, 2023 · 0 comments
Assignees
Labels
bug Something isn't working triage Issue not tagged yet. talking to the user

Comments

@brad-decker
Copy link

Contact Details

No response

What happened?

I was floored when I found this plugin, and the possibilities opened up in front of me in such a way that I was hopeful I had found a way to simplify my current workflow which requires me using a lot of javascript to organize my notes. However, there are two major flaws that prevented me from adopting this that I hope can be resolved.

  1. I really dislike inline fields, it just adds clutter to notes that make it hard to not see the mechanics of how things work when I am in the middle of using the notes to tell a story (using DB folder to keep my campaign for tabletop). I was disturbed to see that any relationship fields I set were being added as inline fields even though I had explicitly not checked the inline fields option.
  2. For some files I already had relations set in properties using the list format or even just text property. When these existed on the same key as a relationship field (On either side for a bi directional. Example: Table A and Table B exist, some notes for Table A have a property for a relationship to Table B. Table B has no properties relating to Table A. On Table B if i tried to connect a row to Table A it would not persist because Table A has a property with the same name as the key I had specified for the relationship in db manager) it prevented DB manager from making any changes to the relationship persist. It would show up on the database view as though it had made the connection but refreshing the db view would remove the recently added connection.

What platform were you using?

Desktop

Version of the plugin

3.5.0

Relevant log output

No response

Are you using the latest version of the plugin in your Obsidian vault?

  • I have verified that I am on the latest version

Are you check if there is a similar issue?

  • I have verified that there are not similar issues
@brad-decker brad-decker added bug Something isn't working triage Issue not tagged yet. talking to the user labels Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Issue not tagged yet. talking to the user
Projects
None yet
Development

No branches or pull requests

2 participants