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

(Feature request) Implement the "new note on top" feature as a boolean label. #3796

Closed
peter-facko opened this issue Apr 3, 2023 · 1 comment

Comments

@peter-facko
Copy link

peter-facko commented Apr 3, 2023

Describe feature

There is a recent feature of changing the position of a new note using the label newNotesOnTop.

Please implement this feature as a boolean label, not based on the label's presence as it is currently.

This would allow the user to make certain subtrees behave differently by making the label inheritable and specifying a different value.

My use case

I personally like having new notes appear at the top in almost all circumstances, which means I use the current implementation's label on the root with inheritable set. The only exception to this are task notes, where I use new notes as updates and those make more sense appearing at the bottom, as chronological order typically goes from the top down.

Additional Information

Alternative approach to this would be to create a feature where a note can define an "anti-label" which explicitly states that the note should appear as if it didn't have the label defined. This, together with inheritable, would make my use case possible as well. The solution would also allow any label feature dealing with the label presence, not just newNotesOnTop, to be more flexible by allowing to make subtree "holes" in the effect area of a label.

@zadam
Copy link
Owner

zadam commented Apr 3, 2023

You can now define #newNotesOnTop=false to negate a #newNotesOnTop set at a higher level. IIRC this pattern has been used in some other cases as well previously.

@zadam zadam closed this as completed Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants