Optimize handleResize and fetchData methods in RepoSummary page

[victorzxj]

What this PR does:
Optimized RepoSummary page: Simplified width calculation logic using widthMap to reduce hardcoding. Streamlined call logic for fetchData, fetchCatalog, and fetchRepoRelations to eliminate code duplication.

Type of changes
Please delete options that are not relevant.

• Code optimization

Feature/Issue validation/testing:

Please describe the tests that you ran to verify your changes and relevant result summary.

• Test1

Test Objective

Verify the optimized code in RepoSummary.vue functions correctly, including:

• Logic within the onMounted lifecycle hook
• Performance of API calls

Test Methodology

1. Unit Testing

   • Simulate different props.repoType values
   • Validate correct invocation of:
     • fetchData
     • fetchCatalog
     • fetchRepoRelations

2. Manual Testing

   • Execute the project and visually verify:
     • Page data loading behavior
     • UI rendering correctness

3. Performance Profiling

   • Measure API call timing
   • Evaluate parallel processing efficiency

Test Steps

1. Functional Verification

   • Run project in test environment
   • Confirm proper display of:
     • README content
     • Dataset information
     • Relationship data

2. Parameter Validation

   • Set props.repoType to:
     • dataset → Verify fetchCatalog invocation
     • model → Verify fetchEndpoint invocation

3. Network Analysis

   • Use browser DevTools to:
     • Check for reduced network requests
     • Confirm parallel request handling

Test Results

✅ Functional Correctness

• Page loads normally
• All data displays accurately

✅ Error Monitoring

• No errors/exceptions detected

Special notes for your reviewer:

Checklist:

• I have added unit/e2e tests that prove your fix is effective or that this feature works.
• I have reviewed my own code and ensured that it follows the project's style guidelines.

Release note:

NONE

MR Summary:

The summary is added by @codegpt.

The MR optimizes the handleResize and fetchData methods in the RepoSummary.vue file. Key updates include:

1. Simplified width calculation logic in handleResize using a widthMap to reduce hardcoding.
2. Streamlined the call logic for fetchData, fetchCatalog, and fetchRepoRelations to eliminate code duplication. These methods are now invoked within fetchData using a unified fetchEndpointData function.
3. The fetchData method now uses Promise.all for parallel processing of API calls, potentially improving performance.
4. The onMounted lifecycle hook has been simplified by removing direct calls to fetchCatalog and fetchRepoRelations, as they are now handled within fetchData.

[starship-github]

MR Evaluation:

This feature is still under test, evaluation are given by AI and might be inaccurate.

After evaluation, the code changes in the Merge Request get score: 75.

Analysis for the evaluation score:

• The code change may not have preprocessed security related exceptions.
• The code change may not include the corresponding user manual.
• The code change may not include the corresponding development documentation.
• If there are API changes, the code change may not include the corresponding API documentation.
• The code change may not include an exception capture mechanism.

Tips

CodeReview Commands (invoked as MR or PR comments)

• @codegpt /review to trigger an code review.
• @codegpt /evaluate to trigger code evaluation process.
• @codegpt /describe to regenerate the summary of the MR.
• @codegpt /secscan to scan security vulnerabilities for the MR or the Repository.
• @codegpt /help to get help.

CodeReview Discussion Chat

There are 2 ways to chat with Starship CodeReview:

• Review comments: Directly reply to a review comment made by StarShip.
  Example:
  • @codegpt How to fix this bug?
• Files and specific lines of code (under the "Files changed" tab):
  Tag @codegpt in a new review comment at the desired location with your query.
  Examples:
  • @codegpt generate unit testing code for this code snippet.

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 MR/PR comments.

CodeReview Documentation and Community

• Visit our Documentation
  for detailed information on how to use Starship CodeReview.

About Us:

Visit the OpenCSG StarShip website for the Dashboard and detailed information on CodeReview, CodeGen, and other StarShip modules.