You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm unsure whether this used to be supported at all (at least not for the past 2 minor versions), but it seems that brief is not preserved when writing to yaml, unlike e.g., label:
A principled approach to this would seem to also require #273, such that auto-generated briefs can skip being written out.
I'm also surprised that this issue hasn't seen a ticket yet - perhaps not many folks are in the business of customizing and recording briefs? @rich-iannone do you have any thoughts on the status of brief? I'm trying to weigh the pros of adding this feature against the cons of maintenance burden that it might come with :)
The text was updated successfully, but these errors were encountered:
I've heard of some people preferring to use the brief field for a longer description of a validation step. Though, I think most would just use the default, automatic generation option (as a good enough description they don't have to write).
It's perhaps for this reason that I didn't preserve brief in the written-out YAML (or, more likely, didn't have a good strategy w.r.t. autobrief at that time). At any rate, I think it really should be part of the pointblank/YAML spec! (and something like what's described in #273 could help).
I'm unsure whether this used to be supported at all (at least not for the past 2 minor versions), but it seems that
brief
is not preserved when writing to yaml, unlike e.g.,label
:A principled approach to this would seem to also require #273, such that auto-generated briefs can skip being written out.
I'm also surprised that this issue hasn't seen a ticket yet - perhaps not many folks are in the business of customizing and recording
brief
s? @rich-iannone do you have any thoughts on the status ofbrief
? I'm trying to weigh the pros of adding this feature against the cons of maintenance burden that it might come with :)The text was updated successfully, but these errors were encountered: