Skip to content
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

fix typo: 'sempahore' -> 'semaphore' #1832

Closed
wants to merge 1 commit into from
Closed

fix typo: 'sempahore' -> 'semaphore' #1832

wants to merge 1 commit into from

Conversation

rrrliu
Copy link
Collaborator

@rrrliu rrrliu commented Jul 19, 2024

thanks @ax0 for flagging!

@rrrliu rrrliu requested review from ichub and ax0 and removed request for ax0 July 19, 2024 20:30
@@ -60,7 +60,7 @@ export function FrogCryptoUpdateTelegramModal({
appConfig.zupassServer,
{
pcd: await credentialManager.requestCredential({
signatureType: "sempahore-signature-pcd"
signatureType: "semaphore-signature-pcd"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is somewhat dangerous, have you thought through the implications?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whoah, crazy that this typo made it into a PCD type name. Changing that is definitely dangerous. If anyone has any of these saved in their PCDCollection (like I do) I'm pretty sure it'll crash on load.

It may be best to just leave the typo in place in the cases where it's part of a data format. Or if we want to fix it, I think we'd need to introduce some notion of type aliases and/or conversion to the PCD framework.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For context this is not a pcd type name, this is the name of something only available in the client - a type of 'credential'

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, so it is. I incorrectly assumed there was a 1:1 mapping. Seems like this is a field in a type with only one value, which is sent but never read. So maybe the compatibility impact is minimal.

@ichub ichub closed this Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants