-
Notifications
You must be signed in to change notification settings - Fork 474
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
Sdk updates for proposed 1.1 spec #197
Draft
mcintyre94
wants to merge
2
commits into
anza-xyz:master
Choose a base branch
from
mcintyre94:sdk-updates-1.1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
import { SOLANA_PROTOCOL } from './constants.js'; | ||
import type { Amount, Label, Memo, Message, Recipient, References, SPLToken } from './types.js'; | ||
import type { Amount, Label, Memo, Message, Recipient, References, SPLToken, Redirect } from './types.js'; | ||
|
||
/** | ||
* Fields of a Solana Pay transaction request URL. | ||
|
@@ -31,18 +31,34 @@ export interface TransferRequestURLFields { | |
message?: Message; | ||
/** `memo` in the [Solana Pay spec](https://github.com/solana-labs/solana-pay/blob/master/SPEC.md#memo). */ | ||
memo?: Memo; | ||
/** `redirect` in the [Solana Pay spec](https://github.com/solana-labs/solana-pay/blob/master/SPEC1.1.md#redirect). */ | ||
redirect?: Redirect; | ||
} | ||
|
||
/** | ||
* Fields of a Solana Pay message sign request URL. | ||
*/ | ||
export interface MessageSignRequestURLFields { | ||
/** `link` in the [Solana Pay spec](https://github.com/solana-labs/solana-pay/blob/master/message-signing-spec.md#link). */ | ||
link: URL; | ||
} | ||
|
||
/** | ||
* Encode a Solana Pay URL. | ||
* | ||
* @param fields Fields to encode in the URL. | ||
*/ | ||
export function encodeURL(fields: TransactionRequestURLFields | TransferRequestURLFields): URL { | ||
return 'link' in fields ? encodeTransactionRequestURL(fields) : encodeTransferRequestURL(fields); | ||
export function encodeURL( | ||
fields: TransactionRequestURLFields | TransferRequestURLFields | MessageSignRequestURLFields | ||
): URL { | ||
return 'link' in fields ? encodeTransactionOrMessageSignRequestURL(fields) : encodeTransferRequestURL(fields); | ||
} | ||
|
||
function encodeTransactionRequestURL({ link, label, message }: TransactionRequestURLFields): URL { | ||
function encodeTransactionOrMessageSignRequestURL({ | ||
link, | ||
label, | ||
message, | ||
}: TransactionRequestURLFields | (MessageSignRequestURLFields & { label: undefined; message: undefined })): URL { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This can also be simplified if we allow those fields. |
||
// Remove trailing slashes | ||
const pathname = link.search | ||
? encodeURIComponent(String(link).replace(/\/\?/, '?')) | ||
|
@@ -68,6 +84,7 @@ function encodeTransferRequestURL({ | |
label, | ||
message, | ||
memo, | ||
redirect, | ||
}: TransferRequestURLFields): URL { | ||
const pathname = recipient.toBase58(); | ||
const url = new URL(SOLANA_PROTOCOL + pathname); | ||
|
@@ -102,5 +119,9 @@ function encodeTransferRequestURL({ | |
url.searchParams.append('memo', memo); | ||
} | ||
|
||
if (redirect) { | ||
url.searchParams.append('redirect', redirect.toString()); | ||
} | ||
|
||
return url; | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think this type can be (structurally) the same as
TransactionRequestURLFields
, right? Label and message can still be used.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.
I think maybe we should rename the type of request to a
Sign Message Request
in the spec and here.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.
They can still be used, but it seems a bit confusing because wallets would presumably ignore them. Both fields are not inputs in the spec, and are also fields in server responses which I think makes it more confusing. We do already have this problem with transaction requests - I just wasn't sure whether it was a good idea to do the same here, and thought it might be better to move toward removing the fields from transaction request in the SDK instead.
Renaming to
Sign Message Request
sounds good to me, seems a bit more natural!