fix: use same ref_id translation for all createmodal

[Axxiar]

m.ref -> m.refId

Summary by CodeRabbit

• Style
  • Updated display labels in forms to improve consistency and clarity for reference fields across the interface.

[coderabbitai]

Walkthrough

The changes update the label properties in several Svelte components used for model forms. In the FrameworkForm, ReferenceControlForm, SolutionForm, and ThreatForm files, the label for the TextField component associated with the reference ID has been changed from m.ref() to m.refId(). In the ReferenceControlForm, the Select component’s label for the csf_function field has also been standardized. No other functionality or public API declarations were modified.

Changes

File(s)	Change Summary
frontend/.../ModelForm/FrameworkForm.svelte frontend/.../ModelForm/SolutionForm.svelte frontend/.../ModelForm/ThreatForm.svelte	Updated the TextField label from m.ref() to m.refId() for the reference ID field.
frontend/.../ModelForm/ReferenceControlForm.svelte	Updated the TextField label for ref_id from m.ref() to m.refId(); standardized the Select label for the csf_function field.

Suggested Reviewers

• nas-tabchiche
• Mohamed-Hacene

Poem

I'm a little rabbit, hopping through the code,
Skipping old labels on every winding road.
Now refId gleams where ref once did reside,
A tiny tweak where clarity takes pride.
With carrot crunches and bytes so light,
I celebrate these changes with a joyful bite!

---

📜 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 aee03c7 and f06e9c2.

📒 Files selected for processing (4)

• frontend/src/lib/components/Forms/ModelForm/FrameworkForm.svelte (1 hunks)
• frontend/src/lib/components/Forms/ModelForm/ReferenceControlForm.svelte (1 hunks)
• frontend/src/lib/components/Forms/ModelForm/SolutionForm.svelte (1 hunks)
• frontend/src/lib/components/Forms/ModelForm/ThreatForm.svelte (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• frontend/src/lib/components/Forms/ModelForm/ReferenceControlForm.svelte

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

• GitHub Check: enterprise-startup-functional-test (3.12)
• GitHub Check: startup-functional-test (3.12)
• GitHub Check: functional-tests (3.12, chromium)
• GitHub Check: startup-docker-compose-test
• GitHub Check: migrations-check (3.12)
• GitHub Check: enterprise-startup-docker-compose-test
• GitHub Check: enterprise-functional-tests (3.12, chromium)
• GitHub Check: Analyze (python)
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (3)

frontend/src/lib/components/Forms/ModelForm/FrameworkForm.svelte (1)

16-16: LGTM! Label standardization looks good.

The change from m.ref() to m.refId() aligns with the PR objective of standardizing reference ID translation.

frontend/src/lib/components/Forms/ModelForm/SolutionForm.svelte (1)

27-27: LGTM! Label standardization looks good.

The change from m.ref() to m.refId() maintains consistency with other components.

frontend/src/lib/components/Forms/ModelForm/ThreatForm.svelte (1)

28-28:

✅ Verification successful

LGTM! Label standardization looks good.

The change from m.ref() to m.refId() completes the standardization across all form components.

Let's verify that all instances have been updated:

---

🏁 Script executed:

#!/bin/bash
# Search for any remaining instances of m.ref() in Svelte files
rg "m\.ref\(\)" "frontend/src/lib/components"

# Search for all instances of m.refId() to confirm standardization
rg "m\.refId\(\)" "frontend/src/lib/components"

Length of output: 1412

---

LGTM! Label standardization looks solid across all form components.
I've confirmed that every instance in the frontend/src/lib/components/Forms/ModelForm directory now uses m.refId() with no remaining instances of m.ref().

---

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. (Beta)
• @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.

[Mohamed-Hacene]

0k