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

fix: remove duplicated action identifier in label #14393

Merged
merged 2 commits into from
Jan 13, 2025
Merged

Conversation

standeren
Copy link
Contributor

@standeren standeren commented Jan 9, 2025

Description

Remove duplicated action identifier in label.

Today:
Skjermbilde 2025-01-09 kl  15 30 54

In this PR:
Skjermbilde 2025-01-09 kl  15 31 06

Related Issue(s)

  • #{issue number}

Verification

  • Your code builds clean without any errors or warnings
  • Manual testing done (required)

Summary by CodeRabbit

  • Language Updates

    • Modified Norwegian language file with updated error messages and UI text
    • Simplified action label formatting by removing dynamic action name references
  • Component Changes

    • Updated action editing components to remove specific action name handling
    • Adjusted test cases to reflect changes in action labeling and editing
  • Testing Updates

    • Modified Playwright tests for process editor actions
    • Simplified action editing method signatures in test pages

@github-actions github-actions bot added area/process Area: Related to app process (e.g. signing, receipt, fill inn, payment, etc). solution/studio/designer Issues related to the Altinn Studio Designer solution. quality/testing Tests that are missing, needs to be created or could be improved. frontend labels Jan 9, 2025
@standeren standeren added skip-releasenotes Issues that do not make sense to list in our release notes team/studio-domain1 skip-documentation Issues where updating documentation is not relevant labels Jan 9, 2025
@standeren standeren force-pushed the fix-text-in-actions branch from 82c73d0 to abf1038 Compare January 9, 2025 15:02
Copy link

codecov bot commented Jan 9, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.65%. Comparing base (84d7de7) to head (d655317).
Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #14393   +/-   ##
=======================================
  Coverage   95.65%   95.65%           
=======================================
  Files        1877     1877           
  Lines       24385    24385           
  Branches     2804     2804           
=======================================
  Hits        23325    23325           
  Misses        799      799           
  Partials      261      261           

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

@standeren standeren linked an issue Jan 13, 2025 that may be closed by this pull request
@ErlingHauan ErlingHauan self-assigned this Jan 13, 2025
Copy link
Contributor

@ErlingHauan ErlingHauan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice cleanup!

@ErlingHauan ErlingHauan added the skip-manual-testing PRs that do not need to be tested manually label Jan 13, 2025
Copy link
Contributor

coderabbitai bot commented Jan 13, 2025

Warning

Rate limit exceeded

@ErlingHauan has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 40 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between abf1038 and d655317.

📒 Files selected for processing (1)
  • frontend/language/src/nb.json (1 hunks)
📝 Walkthrough

Walkthrough

The pull request involves modifications to the frontend of a process editor application, focusing on changes in language configuration, component rendering, and testing. The primary modifications center around removing specific action name references from various components and test files. These changes affect how actions are labeled, displayed, and tested, with a trend towards more generic action handling across the frontend codebase.

Changes

File Change Summary
frontend/language/src/nb.json Removed {{actionName}} from action label translation, simplifying the action label format
frontend/packages/process-editor/src/components/ConfigPanel/EditActions/ActionsEditor.test.tsx Removed actionName: 'reject' from test mocks, reducing test specificity for action buttons
frontend/packages/process-editor/src/components/ConfigPanel/EditActions/ActionsEditor.tsx Eliminated actionName parameter from action label generation
frontend/packages/process-editor/src/components/ConfigPanel/EditActions/EditActions.test.tsx Removed specific action name checks from test assertions
frontend/testing/playwright/pages/ProcessEditorPage/ActionsConfig.ts Changed editAction method to remove action parameter, making action editing more generic
frontend/testing/playwright/tests/process-editor/task-actions.spec.ts Updated editAction method call to remove action parameter

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
🪧 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
frontend/packages/process-editor/src/components/ConfigPanel/ConfigContent/EditActions/EditActions.test.tsx (1)

161-161: LGTM! Consider documenting why renderEditActions is synchronous.

The removal of the unnecessary await improves code clarity. Consider adding a comment explaining that renderEditActions is intentionally synchronous for better maintainability.

+  // renderEditActions is synchronous as it only performs DOM rendering
   renderEditActions();
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6a4ecf9 and abf1038.

📒 Files selected for processing (6)
  • frontend/language/src/nb.json (1 hunks)
  • frontend/packages/process-editor/src/components/ConfigPanel/ConfigContent/EditActions/ActionsEditor/ActionsEditor.test.tsx (0 hunks)
  • frontend/packages/process-editor/src/components/ConfigPanel/ConfigContent/EditActions/ActionsEditor/ActionsEditor.tsx (0 hunks)
  • frontend/packages/process-editor/src/components/ConfigPanel/ConfigContent/EditActions/EditActions.test.tsx (1 hunks)
  • frontend/testing/playwright/pages/ProcessEditorPage/ActionsConfig.ts (1 hunks)
  • frontend/testing/playwright/tests/process-editor/task-actions.spec.ts (1 hunks)
💤 Files with no reviewable changes (2)
  • frontend/packages/process-editor/src/components/ConfigPanel/ConfigContent/EditActions/ActionsEditor/ActionsEditor.tsx
  • frontend/packages/process-editor/src/components/ConfigPanel/ConfigContent/EditActions/ActionsEditor/ActionsEditor.test.tsx
🔇 Additional comments (3)
frontend/testing/playwright/pages/ProcessEditorPage/ActionsConfig.ts (1)

66-73: LGTM! Clean simplification of the editAction method.

The removal of the action parameter and simplification of the button text improves code maintainability by removing redundant action identifier information.

frontend/testing/playwright/tests/process-editor/task-actions.spec.ts (1)

63-63: LGTM! Test updated to match the new method signature.

The test has been correctly updated to use the simplified editAction() method without the action parameter.

frontend/language/src/nb.json (1)

684-684: LGTM! Language string updated to remove duplicated action identifier.

The translation string has been correctly updated to remove {{actionName}}, which aligns with the PR objective of removing duplicated action identifiers from labels.

@ErlingHauan
Copy link
Contributor

ErlingHauan commented Jan 13, 2025

Small PR, so I tested it as well. Works as intended 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/process Area: Related to app process (e.g. signing, receipt, fill inn, payment, etc). frontend quality/testing Tests that are missing, needs to be created or could be improved. skip-documentation Issues where updating documentation is not relevant skip-manual-testing PRs that do not need to be tested manually skip-releasenotes Issues that do not make sense to list in our release notes solution/studio/designer Issues related to the Altinn Studio Designer solution. team/studio-domain1
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

Improve design of Studio components
2 participants