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: stx fallback btn show on load #5665

Merged
merged 1 commit into from
Jul 22, 2024
Merged

fix: stx fallback btn show on load #5665

merged 1 commit into from
Jul 22, 2024

Conversation

alter-eggo
Copy link
Contributor

@alter-eggo alter-eggo commented Jul 19, 2024

Try out Leather build b13d6e3 — Extension build, Test report, Storybook, Chromatic

useAtomValue(stacksAccountState) initially returns empty array on page load, it leads to short display of Connect Stacks btn (which we show in btc only ledger mode)

I believe we need to refactor this and remove usage of atom?
but for now it's prob better just to hide stacks row rather than show fallback btn
wdyt?

Summary by CodeRabbit

  • New Features

    • Enhanced the AssetList component to conditionally display content based on the user's active Stacks account and Ledger key availability.
  • Bug Fixes

    • Improved user experience by preventing unnecessary rendering of the fallback component when no active account or Ledger keys are present.

Copy link

coderabbitai bot commented Jul 19, 2024

Walkthrough

The recent updates to the AssetList component enhance its responsiveness by integrating hooks for managing account and ledger key states. This allows the component to conditionally render its fallback UI based on the presence of an active Stacks account and the availability of Ledger keys, improving user experience by eliminating unnecessary UI elements when not applicable.

Changes

Files Change Summary
src/app/features/asset-list/asset-list.tsx Enhanced AssetList component's logic by incorporating useCurrentStacksAccount and useHasLedgerKeys hooks, allowing conditional rendering of fallback component based on account and Ledger key availability.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant AssetList
    participant CurrentStacksAccountLoader

    User->>AssetList: Render AssetList
    AssetList->>CurrentStacksAccountLoader: Check current account and Ledger keys
    CurrentStacksAccountLoader-->>AssetList: Return account status
    alt Account available and Ledger keys present
        AssetList->>User: Show assets
    else No account or Ledger keys
        AssetList->>User: Render null (no fallback)
    end
Loading

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@alter-eggo alter-eggo requested review from kyranjamie and fbwoolf July 19, 2024 09:18
Comment on lines 20 to 23
const isLedger = useHasLedgerKeys();

if (!currentAccount && !isLedger) return null;

Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't think the loader should ever return something other than child or fallback.

Maybe this should be fixed in the instance of CurrentStacksAccountLoader and not inside of it?

Copy link
Contributor Author

@alter-eggo alter-eggo Jul 19, 2024

Choose a reason for hiding this comment

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

smth like this?

      <CurrentStacksAccountLoader
        fallback={
          !currentAccount && !isLedger ? null : (
            <ConnectLedgerAssetItemFallback
              chain="stacks"
              icon={<StxAvatarIcon />}
              symbol="STX"
              variant={variant}
            />
          )
        }
      >

@alter-eggo alter-eggo marked this pull request as ready for review July 19, 2024 14:00
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f3de110 and b13d6e3.

Files selected for processing (1)
  • src/app/features/asset-list/asset-list.tsx (3 hunks)
Additional comments not posted (2)
src/app/features/asset-list/asset-list.tsx (2)

23-24: LGTM! Imports are correct.

The import statements for useCurrentStacksAccount and useHasLedgerKeys are correct and necessary for the changes made in the component.


39-40: LGTM! Hooks are used correctly.

The useCurrentStacksAccount and useHasLedgerKeys hooks are used correctly to manage the account and ledger key states.

Comment on lines +72 to +79
!currentAccount && !isLedger ? null : (
<ConnectLedgerAssetItemFallback
chain="stacks"
icon={<StxAvatarIcon />}
symbol="STX"
variant={variant}
/>
)
Copy link

Choose a reason for hiding this comment

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

Fix the conditional rendering logic.

The conditional rendering logic for the fallback component is incorrect. The fallback should render null if both currentAccount and isLedger are not present.

-  !currentAccount && !isLedger ? null : (
+  !currentAccount || !isLedger ? null : (
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
!currentAccount && !isLedger ? null : (
<ConnectLedgerAssetItemFallback
chain="stacks"
icon={<StxAvatarIcon />}
symbol="STX"
variant={variant}
/>
)
!currentAccount || !isLedger ? null : (
<ConnectLedgerAssetItemFallback
chain="stacks"
icon={<StxAvatarIcon />}
symbol="STX"
variant={variant}
/>
)

@alter-eggo alter-eggo added this pull request to the merge queue Jul 22, 2024
Merged via the queue into dev with commit 95d6ea5 Jul 22, 2024
30 checks passed
@alter-eggo alter-eggo deleted the fix/fallback-stx branch July 22, 2024 14:05
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