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: Fixed the issue that When switching different node export same file #4597

Merged
merged 1 commit into from
Jan 13, 2025

Conversation

fit2bot
Copy link
Contributor

@fit2bot fit2bot commented Jan 13, 2025

Fixed: Fixed the issue that When switching different node export same file

@fit2bot fit2bot requested a review from a team January 13, 2025 10:00
* 那如果首次点击的树节点,那么此时 url 就会被确定,后续点击的树节点,那么 url 就不会
* 改变了
*/
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 code is looking good overall, it appears there are no known defects or issues at the moment. However, given that we don't know where and when it was last updated, I would recommend updating to ensure there are no bugs introduced over time.

Optimization Suggestions:

  • Use const instead of let for variables that can be modified later, reducing memory usage (though this has minimal effect here).
  • Inlining Object.assign() could improve performance if called often in a similar context, but in this case, it's unlikely as it seems to perform well already.
  • Ensure all references to _tCurrentTreeId_ have proper types set (number)
  • If you decide to add more properties to the dataObj, consider wrapping them into separate constants outside their current scope for clarity
  • Consider using ES6 modules instead of CommonJS modules if the project will eventually move towards Node v8 or beyond

Note: As JavaScript is dynamically typed and its type inference might not catch everything, always do unit tests including edge cases.

Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
C Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@ZhaoJiSen ZhaoJiSen merged commit 5925ac4 into dev Jan 13, 2025
4 of 6 checks passed
@ZhaoJiSen ZhaoJiSen deleted the pr@dev@fixed_export_account branch January 13, 2025 10:01
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