Look into skipping runtime validation of the AceConfig options table
rdw-software opened this issue ยท 0 comments
The high-level API doesn't expose this, but it may be possible to skip the validation when initially creating Rarity's options UI:
In theory this is a cost that needn't be paid on load: Validation can just as easily be performed offline (as part of the test suite).
I don't know if this is really significant, but it's worth considering. The options module may benefit from some restructuring, as it is.
One possible caveat: If custom items need to be validated, they wouldn't be covered. But at first glance, it doesn't look like that matters (?).