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

feat(web): Pension calculator - "Breyta forsendum" button visual changes #16373

Merged
merged 3 commits into from
Oct 11, 2024

Conversation

RunarVestmann
Copy link
Member

@RunarVestmann RunarVestmann commented Oct 11, 2024

Pension calculator - "Breyta forsendum" button visual changes

What

  • Change button to be of the text variant and with an arrow back indicating to the user that he will be going back to the previous page
  • Keep query params when clicking the "EN" or "IS" button in the top right corner so users can change locales without losing their form state

Screenshots / Gifs

Before

Screenshot 2024-10-11 at 14 49 41

Screen.Recording.2024-10-11.at.14.53.02.mov

After

Screenshot 2024-10-11 at 14 50 10

Screen.Recording.2024-10-11.at.14.52.32.mov

Checklist:

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Formatting passes locally with my changes
  • I have rebased against main before asking for a review

Summary by CodeRabbit

  • New Features

    • Enhanced language switching functionality with improved handling of query parameters.
    • Introduced a new ChangeAssumptionsButton for easier navigation within the Pension Calculator results.
  • Improvements

    • Streamlined rendering of internationalization components and organized query parameters for better usability.

@RunarVestmann RunarVestmann added the deprecated:automerge (Disabled) Merge this PR as soon as all checks pass label Oct 11, 2024
@RunarVestmann RunarVestmann requested review from a team as code owners October 11, 2024 14:53
Copy link
Contributor

coderabbitai bot commented Oct 11, 2024

Walkthrough

The changes in this pull request involve updates to the LanguageToggler.tsx and PensionCalculatorResults.tsx components. The LanguageToggler now handles query parameters more effectively when switching languages, while a new ChangeAssumptionsButton component has been introduced in the PensionCalculatorResults, improving the organization of query parameters and internationalization. The modifications streamline the functionality for language toggling and enhance the user interface for managing assumptions within the pension calculator.

Changes

File Change Summary
apps/web/components/LanguageToggler/LanguageToggler.tsx Updated getOtherLanguagePath to handle query parameters and refined logic for path generation. Type updated for LanguageTogglerProps.
apps/web/screens/Organization/SocialInsuranceAdministration/PensionCalculatorResults.tsx Introduced ChangeAssumptionsButton component and modified PensionCalculatorResults to manage query parameters for internationalization. Updated getProps method to include languageToggleQueryParams.

Possibly related PRs

Suggested labels

deploy-feature

Suggested reviewers

  • mannipje

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

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: 1

🧹 Outside diff range and nitpick comments (1)
apps/web/screens/Organization/SocialInsuranceAdministration/PensionCalculatorResults.tsx (1)

281-283: LGTM with a minor typo: changeAssumtionsHref implementation

The changeAssumtionsHref constant is well-implemented, using the linkResolver for consistent routing and appending the queryParamString to preserve the form state. This aligns with the PR objectives.

However, there's a minor typo in the variable name:

-const changeAssumtionsHref = `${
+const changeAssumptionsHref = `${
   linkResolver('pensioncalculator').href
 }?${queryParamString}`
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 38f5c80 and 1573e4f.

📒 Files selected for processing (2)
  • apps/web/components/LanguageToggler/LanguageToggler.tsx (1 hunks)
  • apps/web/screens/Organization/SocialInsuranceAdministration/PensionCalculatorResults.tsx (7 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
apps/web/components/LanguageToggler/LanguageToggler.tsx (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
apps/web/screens/Organization/SocialInsuranceAdministration/PensionCalculatorResults.tsx (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
🔇 Additional comments (4)
apps/web/screens/Organization/SocialInsuranceAdministration/PensionCalculatorResults.tsx (4)

62-71: LGTM: New ChangeAssumptionsButton component looks good

The new ChangeAssumptionsButton component is well-implemented. It follows React best practices, uses TypeScript for type safety, and aligns with the PR objectives by using a text variant button with an arrow back icon. The component is reusable and adheres to the single responsibility principle.


336-345: LGTM: Well-implemented ChangeAssumptionsButton placement

The placement of the ChangeAssumptionsButton within a Hidden component is well-implemented. It manages visibility based on print settings and uses responsive design practices with the justifyContent prop. This implementation aligns with the PR objectives for enhancing the visual design of the "Breyta forsendum" button.


392-394: LGTM: Appropriate placement of ChangeAssumptionsButton in detailed view

The ChangeAssumptionsButton is well-placed within the detailed view, wrapped in a Hidden component for print-only visibility. This ensures the button is available in the appropriate context and follows good practices for managing different output formats.


507-510: LGTM: Effective implementation of language toggle query params

The addition of languageToggleQueryParams is well-implemented. It correctly preserves the query parameters for both 'is' and 'en' languages, ensuring that users can switch between locales without losing their current form state. This aligns perfectly with the PR objectives.

@datadog-island-is
Copy link

datadog-island-is bot commented Oct 11, 2024

Datadog Report

Branch report: feature/web-pension-calculator-comparison
Commit report: 4d4095b
Test service: web

✅ 0 Failed, 84 Passed, 0 Skipped, 33.39s Total Time
➡️ Test Sessions change in coverage: 1 no change

Copy link

codecov bot commented Oct 11, 2024

Codecov Report

Attention: Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.

Project coverage is 36.75%. Comparing base (a26489b) to head (c4324c8).
Report is 3 commits behind head on main.

Files with missing lines Patch % Lines
...suranceAdministration/PensionCalculatorResults.tsx 0.00% 5 Missing ⚠️
...web/components/LanguageToggler/LanguageToggler.tsx 0.00% 3 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #16373      +/-   ##
==========================================
- Coverage   36.75%   36.75%   -0.01%     
==========================================
  Files        6804     6804              
  Lines      140903   140909       +6     
  Branches    40137    40137              
==========================================
  Hits        51785    51785              
- Misses      89118    89124       +6     
Flag Coverage Δ
web 1.83% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...web/components/LanguageToggler/LanguageToggler.tsx 0.00% <0.00%> (ø)
...suranceAdministration/PensionCalculatorResults.tsx 0.00% <0.00%> (ø)

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 06968c0...c4324c8. Read the comment docs.

@kodiakhq kodiakhq bot merged commit 3312179 into main Oct 11, 2024
30 checks passed
@kodiakhq kodiakhq bot deleted the feature/web-pension-calculator-comparison branch October 11, 2024 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deprecated:automerge (Disabled) Merge this PR as soon as all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants