Skip to content

Sd 34 adapt shielder to new designs#24

Merged
rAskVAL merged 6 commits intomainfrom
SD-34-adapt-shielder-to-new-designs
Apr 9, 2025
Merged

Sd 34 adapt shielder to new designs#24
rAskVAL merged 6 commits intomainfrom
SD-34-adapt-shielder-to-new-designs

Conversation

@rAskVAL
Copy link
Contributor

@rAskVAL rAskVAL commented Apr 8, 2025

No description provided.

@aws-amplify-eu-central-1
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-24.d1rxgx3w89g7ku.amplifyapp.com

@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from 9aeae72 to 715970d Compare April 8, 2025 11:22
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from 715970d to 7cb2945 Compare April 8, 2025 11:37
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from ac4126f to 172d7c2 Compare April 8, 2025 13:02
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from 172d7c2 to 66e6bc3 Compare April 8, 2025 14:42
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from 66e6bc3 to d347522 Compare April 8, 2025 16:08
@rAskVAL rAskVAL requested a review from jalooc April 9, 2025 11:40
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from 7913cc3 to df7ca36 Compare April 9, 2025 11:43
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from 98aeda5 to cf4f6a0 Compare April 9, 2025 12:13
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from cf4f6a0 to fa37d67 Compare April 9, 2025 12:17
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from fa37d67 to 6f6f6c4 Compare April 9, 2025 12:30
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from 6f6f6c4 to 80ba876 Compare April 9, 2025 12:37
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from 80ba876 to 906c8b5 Compare April 9, 2025 12:51
Copy link
Contributor

@jalooc jalooc left a comment

Choose a reason for hiding this comment

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

Nice and clean - amazing 🏆 🎖️


2 notes wrt the comments I've left:

  • some of them relate to multiple occurrences of the issue in question - for each issue I have left a comment only on one occurrence of them, so please make sure you find and address all,
  • you were pushing like crazy during my review, so many of the files I commented on are outdated - I'm sure you'll manage to map the comments to the new code ;)

tokenDecimals: (tokenAddress: Address) => ['token-decimals', tokenAddress] as const,
tokenName: (tokenAddress: Address) => ['token-name', tokenAddress] as const,
tokenSymbol: (tokenAddress: Address) => ['token-symbol', tokenAddress] as const,
tokenDecimals: (tokenAddress: Address | 'native') => ['token-decimals', tokenAddress] as const,
Copy link
Contributor

Choose a reason for hiding this comment

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

In other apps we're doing null for native. I dislike using string | 'specific-string' because such a union always evaluate as just string, which makes the type less readable and easier to make a mistake.

But if it's too much work to change, then don't bother.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ill create ticket, it makes sense to use null.

if (!walletAddress || !chainId) return;

console.error('Shielding failed:', error);
void queryClient.invalidateQueries({
Copy link
Contributor

Choose a reason for hiding this comment

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

Invalidation on onError? Shouldn't this be onSuccess?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sometimes if it fails fee still can be taken, so I refetch native balance.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ouukay. Maybe leave a comment with that information then?

@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from 906c8b5 to f9d9d8f Compare April 9, 2025 14:32
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from f9d9d8f to 7692cb9 Compare April 9, 2025 15:40
@rAskVAL rAskVAL force-pushed the SD-34-adapt-shielder-to-new-designs branch from 7692cb9 to 54c5cb1 Compare April 9, 2025 15:48
@rAskVAL rAskVAL merged commit 7b706c7 into main Apr 9, 2025
10 checks passed
@rAskVAL rAskVAL deleted the SD-34-adapt-shielder-to-new-designs branch April 9, 2025 16:17
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.

2 participants