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

Fixed: Export Button Logic Differentiation #4618

Merged
merged 1 commit into from
Feb 7, 2025
Merged

Conversation

ZhaoJiSen
Copy link
Member

No description provided.

@fit2bot fit2bot requested a review from a team February 7, 2025 03:20
*/
return Object.assign({}, this.exportOptions, { url: this.tableUrl })
return Object.assign(this.exportOptions, { url: this.tableUrl })
}
},
methods: {
Copy link
Member

Choose a reason for hiding this comment

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

The provided code seems to define a Vue component that exports an asset account list page. The method exportOptions has been updated from using the partialRight function incorrectly with assignIfNot and reusing it with Object.assign instead.

The main issue is related to URL assignment when navigating assets lists between nodes or after exporting. Currently, if there's no explicit change on navigation or export options, subsequent calls to /accounts/account-secrets/ will not lead to different URLs. This needs modification according to the current scenario:

  • After successfully switching back to the tree view mode (account details), you may want to adjust how exported URLs are determined based on the user interaction. For instance:
    exportDefaultMethods() {
      this.importTreeNode(false);

In general, these issues should be addressed to ensure consistent behavior across both views while also improving error handling for invalid or unexpected behaviors.

Copy link

sonarqubecloud bot commented Feb 7, 2025

@feng626 feng626 merged commit 1e381b0 into dev Feb 7, 2025
4 of 6 checks passed
@feng626 feng626 deleted the pr@der@fixed_export_switch branch February 7, 2025 03:21
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