Can we conditionally lock/disable our @editable attributes yet? Best workaround?

The first screenshot in the @editable documentation shows “Priority Group” is greyed-out (not currently editable), due to other factors.
Can we do that yet?

No rush, I know you guys are super busy reducing Verse’s reliance on device-actors - which we love! keep up the good work! I don’t see it on the timeline but I thought Phil said this was a 2024 ambition.

As a work-around, i’m considering an array of 0/1 length to act as a toggle… or maybe something silly with graph components…

Does anyone have a good workaround?

Update:
I just realised I can use Option’s, and the UEFN Editor makes a nice “Set To Value” button, and a set value can then be deleted - This has helped clean up my game-manager immensely for things like “Does this group have a max-size?”.
Super keen for more ideas from the community <3

Edit:
BTW, clamping values with the type macro works in code, but UEFN editor ignores it when it’s an optional.

@editable
MaxPower:type{X:int where 1<=X, X<=100} = 100
@editable
MaybeMaxTries:?type{X:int where 1<=X, X<=100} = false

^^
Fails to build if I default MaybeMaxTries := option{111}
But if I drag the slider in UEFN editor it can go out of range (not clamped like MaxPower)