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
While running the test repeatedly, I noticed that the time it takes to do a validation is quite high, around 2-5ms per check. With some debugging, I noticed that most of that time is from the runtime checks on the options and presets by yup.
Considering that the options and preset will be hardcoded, yup could be disabled in the production build to significantly cut on runtime. For example, the tests for the blank symbol ? take between 100ms and 200ms with yup enabled, but around 2ms with up disabled.
The text was updated successfully, but these errors were encountered:
While running the test repeatedly, I noticed that the time it takes to do a validation is quite high, around 2-5ms per check. With some debugging, I noticed that most of that time is from the runtime checks on the options and presets by yup.
Considering that the options and preset will be hardcoded, yup could be disabled in the production build to significantly cut on runtime. For example, the tests for the blank symbol
?
take between 100ms and 200ms with yup enabled, but around 2ms with up disabled.The text was updated successfully, but these errors were encountered: