ux: support optional hints #898

Open
opened 2025-07-03 02:51:56 +00:00 by jade · 0 comments
Owner

For things like #897, it's possible that we might want to write an opt out warning for doing cli usage patterns that look like they might be a mistake. git and jj support such an idea, e.g. the detached head hint.

I think this is likely blocked on config format evolution, but I'm wondering if we can more creatively use our existing format as well: can we use dots in option names in anticipation of moving to a config format that supports real nesting?

For things like #897, it's possible that we might want to write an opt out warning for doing cli usage patterns that look like they might be a mistake. git and jj support such an idea, e.g. the detached head hint. I think this is likely blocked on config format evolution, but I'm wondering if we can more creatively use our existing format as well: can we use dots in option names in anticipation of moving to a config format that supports real nesting?
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix#898
No description provided.