chore: updated text for deletion page and component

[JamalAlabdullah]

Description

Updated the text for nativ popover when we delete page or component in utforming.

Related Issue(s)

• Update delete pop-up messsage on pages, components and code list #14706

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Summary by CodeRabbit

• Style
  • Updated deletion confirmation messages for components and pages to simplify the wording and clearly indicate that all associated dependencies will be removed.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes update deletion confirmation text strings in the language file. Both the component and page deletion messages have been simplified by replacing references to "Summary-komponenter" with "avhengigheter" and streamlining the wording.

Changes

File	Change Summary
frontend/language/src/nb.json	Updated deletion confirmation messages: modified ux_editor.component_deletion_text and ux_editor.page_delete_text for clarity and consistency.

Possibly related PRs

• feat: remove summary from componentlist and rename summary2 #14557: Modifies deletion confirmation messages in the same language file, targeting similar text updates.

Suggested labels

kind/chore, skip-manual-testing, skip-documentation

Suggested reviewers

• Jondyr
• github-actions

---

📜 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 b7e4993 and b817b54.

📒 Files selected for processing (1)

• frontend/language/src/nb.json (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• frontend/language/src/nb.json

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

• GitHub Check: Build environment and run e2e test
• GitHub Check: CodeQL
• GitHub Check: Testing
• GitHub Check: Typechecking and linting

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.76%. Comparing base (64b8511) to head (b817b54).
Report is 7 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #14708   +/-   ##
=======================================
  Coverage   95.76%   95.76%           
=======================================
  Files        1914     1914           
  Lines       24947    24947           
  Branches     2856     2856           
=======================================
  Hits        23890    23890           
  Misses        798      798           
  Partials      259      259           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lassopicasso]

I think we should keep this as two separate text keys—one for pages and one for components—while adjusting the text based on @Annikenkbrathen's suggestion. That seems better than komponenten/siden.

Edit, if we want to keep one text key, maybe "Er du sikker på at du vil slette? Alle avhengigheter til denne vil også bli slettet."
@Ildest, do you have a suggestion?

[Ildest]

Member

Not sure if I have understood this correctly, but I think it is important that we say what we are deleting, so maybe keep the text and say "Er du sikker på at du vil slette siden? Alle avhengigheter tilden blir også slettet." Og det samme for komponent.

If the suggestion is to merge the massages and have "siden/komponenten" it is OK, but no ideal. A separate message for each is clearer to the user, and we already have that for group.

[Ildest]

Looks good :-).