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
When defining the schema of our rate limiter, it's hard to ignore or rather distinguish between Redis values set by configuration, vs Redis values set by the application.
cb: Controller;
class Controller {
toggle: Boolean = false; // off by default
hidden rate: UInt16 // internal calculation
}
There is also perhaps an edge case (really shouldn't happen), when the config is altered by the running application. I am not sure how to mark this up! Readonly vs Write ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When defining the schema of our rate limiter, it's hard to ignore or rather distinguish between Redis values set by configuration, vs Redis values set by the application.
I'm thinking of capturing it with the hidden attribute, but I am not sure that's right? https://pkl-lang.org/main/current/language-reference/index.html#hidden-properties
There is also perhaps an edge case (really shouldn't happen), when the config is altered by the running application. I am not sure how to mark this up! Readonly vs Write ?
Beta Was this translation helpful? Give feedback.
All reactions