[WEB-3479] fix: module flicker issue on property updation

[gakshita]

Description

This PR fixes the module property flicker issue on updation.

Summary by CodeRabbit

• Refactor
  • Adjusted the module update process so that after updating, the latest module information isn’t automatically refreshed. You may need to manually refresh your view to see the most current details. All error safeguards remain in place as before.

[coderabbitai]

Walkthrough

This change removes the automatic call to fetchModuleDetails from the updateModuleDetails method in the ModulesStore class. As a result, after a module update, the store no longer immediately retrieves the updated module details from the backend. The error handling remains the same, reverting changes upon a failed update. This adjustment alters the control flow by relying on a manual refresh for obtaining the latest module data.

Changes

File Path	Summary
web/.../module.store.ts	Removed the immediate call to fetchModuleDetails in updateModuleDetails; control flow updated to skip auto-fetch of module details.

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant ModulesStore
    participant Backend

    App->>ModulesStore: updateModuleDetails(data)
    ModulesStore->>Backend: patchModule(data)
    Backend-->>ModulesStore: success
    note right of ModulesStore: (Auto-fetch of updated details removed)

Loading

Suggested labels

🐛bug, 🌐frontend

Suggested reviewers

• sriramveeraghanta
• SatishGandham

Poem

I'm a little rabbit, coding all day,
Hopping through changes in a playful way.
The auto-fetch is gone, like a shadow in the night,
Manual refresh now brings the data to light.
With floppy ears and a code-filled heart,
I celebrate these updates—a fresh, new start!
(_/)\n( •_•)\n/ >🐰 Hop on, let’s code smart!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c021ffd and a9df5f5.

📒 Files selected for processing (1)

• web/core/store/module.store.ts (0 hunks)

💤 Files with no reviewable changes (1)

• web/core/store/module.store.ts

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.