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

Question on the usage of levels #586

Open
maztentropy opened this issue Dec 2, 2022 · 0 comments
Open

Question on the usage of levels #586

maztentropy opened this issue Dec 2, 2022 · 0 comments
Labels

Comments

@maztentropy
Copy link

Could the general usage of this attribute be clarified a bit further?

  • When using doorstop add REQ the new item seems to be assigned a ".n+1" to the highest existing level (where n is the highest sublevel).
    • E.g.: If my highest level is 20 and I've already created 3 elements in that level my new item will be assigned a 20.4.
  • -l can be used to specify the exact level of the item you wish to create but if that level already exists it will be taken from the other item that holds it.
  • Is there any way to create a new item given a level (say "1") but just use the next one available?
    • E.g.: 1.1, 1.2, 1.3 & 2.1 already exist and I would like to create the next available level 1 (1.4) without necessarily knowing how many have been taken already?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants