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

FR: if the page of the namespace has a deck/tag property, use it by default #255

Open
thiswillbeyourgithub opened this issue Mar 11, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@thiswillbeyourgithub
Copy link

Describe the solution you'd like
When a card block has no deck:: or tags:: property, your app searches among the parents recursively until the root of the page. If none are found the default deck is used and no tags are added. I think it would be better if :

  1. if no deck:: property was found in the page, check if one is given in the page the defines the namespace of the page (if the page is in a namespace).
  2. search for tags:: properties also in the page of the namespace and add it to the card.

Example:

  • A block role of the mitochondria ? :-> the mitochondria is the powerhouse of the cell in the page unversity___freshman___biology___cell_functions
  • the page university_freshman___biology could contain properties deck:: biology and tags:: biology and they would be taken into account for blocks in cell functions.
    This can seem useless but there are cases where you create many pages in a namespace and having to specify those tags and deck over and over seems silly.

Describe how it will help your workflow
It would make it easier to add default tags and deck per namespace.

Describe alternatives you've considered
Adding those properties my self each and every time.

@thiswillbeyourgithub thiswillbeyourgithub added the enhancement New feature or request label Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant