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
Currently Priorities can take any number value, it would be better if there were some limit on the values you could provide. It seems like allowing any number could turn into mayhem.
We think an enumeration for these values would be nice. We also considered typing Priority, but we want to start with enumeration.
The text was updated successfully, but these errors were encountered:
classPriorityextendsEnumerationValue{// Priority levels that can be used by Utterances providing the `announcerOptions.priority` option.publicstaticTOP_PRIORITY=newPriority(10);publicstaticHIGH_PRIORITY=newPriority(5);publicstaticMEDIUM_PRIORITY=newPriority(2);publicstaticDEFAULT_PRIORITY=newPriority(DEFAULT_PRIORITY);publicstaticLOW_PRIORITY=newPriority(0);publicconstructor(publicreadonlypriorityNumber: number){super();}publicstaticenumeration=newEnumeration(Priority);}
I kinda like just having a number. It makes things a bit more flexible and so far we haven't run into trouble. Closing, but please reopen if you disagree.
Currently Priorities can take any number value, it would be better if there were some limit on the values you could provide. It seems like allowing any number could turn into mayhem.
We think an enumeration for these values would be nice. We also considered typing Priority, but we want to start with enumeration.
The text was updated successfully, but these errors were encountered: