-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command Parser #2716
base: v5
Are you sure you want to change the base?
Command Parser #2716
Conversation
motivated by wanting to return a read only array from the parser object
} | ||
|
||
setCachable() { | ||
this.#cachable = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is cachable "dynamic" (can be either true
or false
depending on the command arguments)? if not, we should move it from the parser to a constant property on the command.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
client = redirectTo; | ||
|
||
const chainId = Symbol('Asking Chain'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this fix part of another PR too?
Description
Start of implementation of changing how command arguments are transformed to enable easier and more consistent usage across the different clients we have and to enable client side caching.
Checklist
npm test
pass with this change (including linting)?