-
Notifications
You must be signed in to change notification settings - Fork 434
feat(lld, llm): target a custom reference of the CAL #10507
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
feat(lld, llm): target a custom reference of the CAL #10507
Conversation
The latest updates on your projects. Learn more about Vercel for Git βοΈ
3 Skipped Deployments
|
859dce9
to
3a4eb17
Compare
3a4eb17
to
cd18afd
Compare
5735489
cd18afd
to
5735489
Compare
|
signatureKind = "prod", | ||
ref = getEnv("CAL_REF") || undefined, |
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.
Why don't we use the test
signatureKind
when not on the main branch ?
Because usually we won't have a prod signature if the branch is not main
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.
We don't use test
because these signatures are not working at the moment, making this feature impossible to use...
A prod
signature has been added on purpose here in order to make it work.
Maybe we can add a TODO
explaining the situation ?
const ref = useEnv("CAL_REF"); | ||
const [inputValue, setInputValue] = useState(ref || "branch:next"); |
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.
maybe you could add a default value in env. file?
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.
Default is empty because in the nominal case, it must be empty as we want the CAL to select its own default (asserting LL always know the default is quite big).
I want this env filled only with an explicit action from the user.
prepareCurrency: (currency: CryptoCurrency) => Promise<unknown | null | undefined>; | ||
prepareCurrency: ( | ||
currency: CryptoCurrency, | ||
{ forceUpdate }?: { forceUpdate: boolean }, |
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.
[ASK] why do you need an object?
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.
Because it is easier to understand what happens with prepareCurrency(coin, { forceUpdate: true })
as opposed to prepareCurrency(coin, true)
that does not give much context.
β Checklist
npx changeset
was attached.π Description
Allow developers to target a specific version of the CAL for test purposes.
Expose
SPECULOS_API_PORT
as global env, passing by.β Context
π§ Checklist for the PR Reviewers