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(regulations-admin): date format signature, remove self affect, disclaimer text #16288

Merged
merged 3 commits into from
Oct 7, 2024

Conversation

thordurhhh
Copy link
Member

@thordurhhh thordurhhh commented Oct 7, 2024

What

Update date format in signature, remove self affect, update disclaimer text.

Commented out self affect removal kept in for purpose, we're not sure if we want to keep it, but it will be out for testing purposes.

Why

Updating after comments from review.

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

    • Introduced a new date formatting utility for improved clarity in signature text.
    • Added a function to format dates according to Icelandic conventions.
  • Bug Fixes

    • Enhanced control flow in the ImpactBaseSelection component to prevent rendering when no options are available.
  • Documentation

    • Updated message descriptors to clarify conditions for amending regulations.

@thordurhhh thordurhhh added the automerge Merge this PR as soon as all checks pass label Oct 7, 2024
@thordurhhh thordurhhh requested a review from a team as a code owner October 7, 2024 11:00
Copy link
Contributor

coderabbitai bot commented Oct 7, 2024

Walkthrough

The changes in this pull request involve several updates across multiple files within the regulations administration module. A new utility function formatDate is introduced for date formatting, which replaces an existing parameter in the getDefaultSignatureText function. The ImpactBaseSelection component is modified to return null when there are no options available. Additionally, a message descriptor in messages.ts is updated for clarity regarding regulation amendments. Other changes include the restructuring of functions in formatAmendingRegulation.ts and the disabling of a specific option in the useAffectedRegulations hook.

Changes

File Change Summary
libs/portals/admin/regulations-admin/src/components/EditSignature.tsx Introduced formatDate utility function; modified getDefaultSignatureText to remove dateFormatter parameter and use formatDate(new Date()) instead. Updated EditorInput component to reflect changes in function signature.
libs/portals/admin/regulations-admin/src/components/impacts/ImpactBaseSelection.tsx Added a conditional check to return null if mentionedOptions array is empty, preventing rendering of the Select component when there are no options.
libs/portals/admin/regulations-admin/src/lib/messages.ts Updated message descriptor ap.regulations-admin:draft-impactedreg-explainer to clarify conditions for amending regulations.
libs/portals/admin/regulations-admin/src/utils/formatAmendingRegulation.ts Removed internal formatDate function and updated formatAffectedAndPlaceAffectedAtEnd to use the new formatDate utility function for date formatting.
libs/portals/admin/regulations-admin/src/utils/formatAmendingUtils.ts Introduced new formatDate function for date formatting using Icelandic locale.
libs/portals/admin/regulations-admin/src/utils/hooks.ts Commented out code that added a self-referential option to the mentionedOptions array in the useAffectedRegulations function, altering its behavior.

Possibly related PRs

Suggested labels

high priority

Suggested reviewers

  • thorkellmani
  • albinagu

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

codecov bot commented Oct 7, 2024

Codecov Report

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

Project coverage is 36.86%. Comparing base (8c77303) to head (73f879c).
Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
...regulations-admin/src/utils/formatAmendingUtils.ts 0.00% 7 Missing ⚠️
...min/src/components/impacts/ImpactBaseSelection.tsx 0.00% 2 Missing ⚠️
...regulations-admin/src/components/EditSignature.tsx 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #16288      +/-   ##
==========================================
- Coverage   36.86%   36.86%   -0.01%     
==========================================
  Files        6798     6796       -2     
  Lines      140482   140480       -2     
  Branches    39934    39935       +1     
==========================================
- Hits        51792    51790       -2     
  Misses      88690    88690              
Flag Coverage Δ
api 3.37% <ø> (ø)
application-system-api 41.68% <ø> (ø)
application-template-api-modules 24.27% <ø> (-0.04%) ⬇️
application-templates-parental-leave 30.03% <ø> (+0.12%) ⬆️
application-ui-shell 21.27% <ø> (ø)
portals-admin-regulations-admin 1.88% <0.00%> (-0.01%) ⬇️
testing-e2e ?

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

Files with missing lines Coverage Δ
...ortals/admin/regulations-admin/src/lib/messages.ts 0.00% <ø> (ø)
...ations-admin/src/utils/formatAmendingRegulation.ts 0.00% <ø> (ø)
...portals/admin/regulations-admin/src/utils/hooks.ts 0.00% <ø> (ø)
...regulations-admin/src/components/EditSignature.tsx 0.00% <0.00%> (ø)
...min/src/components/impacts/ImpactBaseSelection.tsx 0.00% <0.00%> (ø)
...regulations-admin/src/utils/formatAmendingUtils.ts 0.00% <0.00%> (ø)

... and 2 files with indirect coverage changes


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 18373d4...73f879c. Read the comment docs.

@datadog-island-is
Copy link

datadog-island-is bot commented Oct 7, 2024

Datadog Report

All test runs f0f89a5 🔗

6 Total Test Services: 0 Failed, 6 Passed
⬆️ Test Sessions change in coverage: 1 increased (+0.1%), 11 no change

Test Services
Service Name Failed Known Flaky New Flaky Passed Skipped Total Time Code Coverage Change Test Service View
api 0 0 0 4 0 2.61s 1 no change Link
application-system-api 0 0 0 120 2 2m 58.72s 1 no change Link
application-template-api-modules 0 0 0 134 0 2m 1.91s 1 no change Link
application-templates-parental-leave 0 0 0 162 0 20.14s 1 increased (+0.1%) Link
application-ui-shell 0 0 0 74 0 35.23s 1 no change Link
portals-admin-regulations-admin 0 0 0 24 0 14.63s 1 no change Link

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

🧹 Outside diff range and nitpick comments (6)
libs/portals/admin/regulations-admin/src/components/impacts/ImpactBaseSelection.tsx (1)

47-49: Approved: Good addition to prevent rendering empty select input.

The new condition effectively prevents rendering the Select component when there are no options available. This improves the component's behavior and aligns with best practices for reusable components.

Consider adding a message or placeholder element when there are no options, to provide feedback to the user. For example:

if (!mentionedOptions.length) {
  return <Text>{t(impactMsgs.noOptionsAvailable)}</Text>;
}

This would enhance the user experience by explicitly communicating the lack of options.

libs/portals/admin/regulations-admin/src/utils/hooks.ts (1)

94-98: Consider adding a comment explaining the commented-out code

The removal of the self-affect option aligns with the PR objectives. However, since the PR summary mentions keeping this available for testing purposes, it would be beneficial to add a comment explaining why this code is commented out and how it can be used for testing if needed.

Consider adding a comment like this above the commented-out code:

// Commented out for now as per PR #16288. Kept for potential testing purposes.
// Uncomment to re-enable self-affect option if needed.

This will provide context for future developers and align with the stated intention in the PR objectives.

libs/portals/admin/regulations-admin/src/utils/formatAmendingUtils.ts (1)

120-130: LGTM: Well-implemented formatDate function with a minor suggestion.

The formatDate function is well-implemented, adhering to TypeScript usage and providing a reusable utility for date formatting with Icelandic locale. It handles potential undefined dates and efficiently removes leading zeros.

A minor suggestion for improvement:

Consider using optional chaining and nullish coalescing for a more concise implementation:

export const formatDate = (date: Date) => {
  return format(date, 'dd. MMMM yyyy', { locale: is })
    .replace(/^0+/, '') // Remove leading zeros
    ?? '';
}

This approach eliminates the need for the explicit if-else statement and the creation of a new Date object.

libs/portals/admin/regulations-admin/src/components/EditSignature.tsx (1)

Line range hint 30-44: Approved: Simplified getDefaultSignatureText function with consistent date formatting.

The changes to the getDefaultSignatureText function are well-implemented:

  1. The function signature is simplified by removing the dateFormatter parameter.
  2. The use of the imported formatDate function ensures consistent date formatting across the application.

These changes align with the PR objectives and improve the overall code quality.

Consider adding a brief comment explaining the purpose of the formatDate function for better code documentation:

// Format the current date for the signature text
.replace('{dags}', formatDate(new Date()))
libs/portals/admin/regulations-admin/src/utils/formatAmendingRegulation.ts (1)

Line range hint 89-91: Improved code organization with external formatDate function

The removal of the internal formatDate function and use of the imported one improves code organization and reduces duplication. This change enhances maintainability and aligns with the principle of separation of concerns.

Consider adding a type annotation for the date parameter to enhance type safety:

formatDate(item.date as Date)

This ensures that the formatDate function receives the expected type and helps prevent potential runtime errors.

libs/portals/admin/regulations-admin/src/lib/messages.ts (1)

412-412: Approved with a minor suggestion for clarity.

The updated message provides clearer guidance on when and how to reference other regulations. This aligns well with the PR objectives of revising the disclaimer text.

To further enhance clarity, consider adding a brief example:

- 'ATH: Sé ætlunin að breyta annarri reglugerð, þarf að minnast á þá reglugerð með skýrum hætti í þessari stofnreglugerð.',
+ 'ATH: Sé ætlunin að breyta annarri reglugerð, þarf að minnast á þá reglugerð með skýrum hætti í þessari stofnreglugerð. Til dæmis: "Reglugerð nr. XXX/YYYY er hér með breytt sem hér segir: ..."',

This addition provides a concrete example of how to reference another regulation, which could help users better understand and follow the guideline.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 600ae64 and a4aa4c5.

📒 Files selected for processing (6)
  • libs/portals/admin/regulations-admin/src/components/EditSignature.tsx (3 hunks)
  • libs/portals/admin/regulations-admin/src/components/impacts/ImpactBaseSelection.tsx (1 hunks)
  • libs/portals/admin/regulations-admin/src/lib/messages.ts (1 hunks)
  • libs/portals/admin/regulations-admin/src/utils/formatAmendingRegulation.ts (1 hunks)
  • libs/portals/admin/regulations-admin/src/utils/formatAmendingUtils.ts (2 hunks)
  • libs/portals/admin/regulations-admin/src/utils/hooks.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (6)
libs/portals/admin/regulations-admin/src/components/EditSignature.tsx (1)

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

  • Reusability of components and hooks across different NextJS apps.
  • TypeScript usage for defining props and exporting types.
  • Effective tree-shaking and bundling practices."
libs/portals/admin/regulations-admin/src/components/impacts/ImpactBaseSelection.tsx (1)

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

  • Reusability of components and hooks across different NextJS apps.
  • TypeScript usage for defining props and exporting types.
  • Effective tree-shaking and bundling practices."
libs/portals/admin/regulations-admin/src/lib/messages.ts (1)

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

  • Reusability of components and hooks across different NextJS apps.
  • TypeScript usage for defining props and exporting types.
  • Effective tree-shaking and bundling practices."
libs/portals/admin/regulations-admin/src/utils/formatAmendingRegulation.ts (1)

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

  • Reusability of components and hooks across different NextJS apps.
  • TypeScript usage for defining props and exporting types.
  • Effective tree-shaking and bundling practices."
libs/portals/admin/regulations-admin/src/utils/formatAmendingUtils.ts (1)

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

  • Reusability of components and hooks across different NextJS apps.
  • TypeScript usage for defining props and exporting types.
  • Effective tree-shaking and bundling practices."
libs/portals/admin/regulations-admin/src/utils/hooks.ts (1)

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

  • Reusability of components and hooks across different NextJS apps.
  • TypeScript usage for defining props and exporting types.
  • Effective tree-shaking and bundling practices."
🔇 Additional comments (9)
libs/portals/admin/regulations-admin/src/components/impacts/ImpactBaseSelection.tsx (1)

Line range hint 1-63: LGTM: Component adheres to coding guidelines and best practices.

The ImpactBaseSelection component is well-structured and follows the coding guidelines for files in the libs directory:

  1. It uses TypeScript effectively for prop definitions and type exports.
  2. The component is designed for reusability across different NextJS apps.
  3. Its small size and focused functionality contribute to effective tree-shaking and bundling.

The component's implementation is clean and maintainable, making good use of hooks and external utilities.

libs/portals/admin/regulations-admin/src/utils/formatAmendingUtils.ts (2)

2-3: LGTM: New imports are appropriate and follow best practices.

The new imports for the format function and Icelandic locale from date-fns are correctly added. They support the new formatDate function and follow the existing import style. The specific imports also facilitate effective tree-shaking.


Line range hint 1-130: Confirms adherence to coding guidelines for libs/**/* files.

The changes in this file comply with the specified coding guidelines:

  1. The new formatDate function is reusable across different NextJS apps.
  2. TypeScript is used to define the input type of the function.
  3. The specific imports from date-fns support effective tree-shaking and bundling practices.
libs/portals/admin/regulations-admin/src/components/EditSignature.tsx (3)

23-23: LGTM: New import statement for formatDate.

The addition of the formatDate import is appropriate for the changes made in the getDefaultSignatureText function. It follows good practices by importing only the necessary function and using a relative import path.


162-162: LGTM: Updated getDefaultSignatureText function call.

The change in the EditorInput component is consistent with the updated getDefaultSignatureText function signature. It correctly removes the formatDateFns argument, simplifying the component usage while maintaining the existing functionality.


Line range hint 1-238: Overall assessment: Well-implemented changes that improve code quality and consistency.

The modifications in this file successfully address the PR objectives related to updating the date format in the signature. The changes demonstrate good coding practices:

  1. Improved reusability by centralizing date formatting logic.
  2. Simplified API by removing unnecessary parameters.
  3. Consistent use of TypeScript for type definitions.

These updates enhance the maintainability and consistency of the regulations admin module.

To ensure that the changes don't introduce any unintended side effects, please run the following verification script:

✅ Verification successful

Verification Successful: All instances of dateFormatter have been removed, and getDefaultSignatureText is correctly implemented in EditSignature.tsx.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the formatDate function is used consistently across the codebase

# Test: Search for any remaining instances of dateFormatter to ensure complete migration
rg --type typescript 'dateFormatter'

# Test: Check for any other usages of getDefaultSignatureText to ensure they've been updated
rg --type typescript 'getDefaultSignatureText'

Length of output: 153


Script:

#!/bin/bash
# Description: Verify that the formatDate function is used consistently across the codebase

# Test: Search for any remaining instances of dateFormatter to ensure complete migration
rg 'dateFormatter' --glob '*.ts' --glob '*.tsx'

# Test: Check for any other usages of getDefaultSignatureText to ensure they've been updated
rg 'getDefaultSignatureText' --glob '*.ts' --glob '*.tsx'

Length of output: 341

libs/portals/admin/regulations-admin/src/utils/formatAmendingRegulation.ts (2)

13-13: Improved modularity with formatDate import

The addition of the formatDate import from a separate utility file enhances code modularity and reusability. This change aligns well with best practices for maintaining clean and efficient code structure.


Line range hint 1-589: Compliance with coding guidelines and best practices

The changes in this file adhere to the coding guidelines for the libs directory:

  1. The modifications maintain reusability across different NextJS apps.
  2. TypeScript is used consistently for type definitions and exports.
  3. The changes don't introduce new exports, preserving the existing interface which is good for tree-shaking.

The overall structure of the file remains consistent, and the changes improve modularity without compromising the existing functionality.

libs/portals/admin/regulations-admin/src/lib/messages.ts (1)

Line range hint 1-1024: File review summary: Meets coding guidelines and best practices.

This file adheres to the coding guidelines for libs/**/*:

  1. It supports reusability across different NextJS apps by exporting message descriptors.
  2. TypeScript is used effectively for defining props and exporting types.
  3. The structure of the file, with separate defineMessages calls, supports effective tree-shaking and bundling.

The changes made improve the clarity of the regulations amendment process without compromising the file's overall structure or best practices.

@thordurhhh thordurhhh added automerge Merge this PR as soon as all checks pass and removed automerge Merge this PR as soon as all checks pass labels Oct 7, 2024
@kodiakhq kodiakhq bot merged commit dcd0002 into main Oct 7, 2024
43 checks passed
@kodiakhq kodiakhq bot deleted the regulations-admin/date-self-affect-warn branch October 7, 2024 17:32
thordurhhh added a commit that referenced this pull request Oct 8, 2024
…sclaimer text (#16288)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
kodiakhq bot added a commit that referenced this pull request Oct 11, 2024
…-pages (#16234)

* Service portal removal. Add portals my pages

* minor fixes

* Fix

* path fix

* fix(portals-admin): locklist (#16279)

* fix(portals-admin): locklist

* tweak

* msg id fix

* tweak

---------

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* feat(service-portal): feature flag resolver for documents (#16285)

* fix: def info and alert

* feat: add feature flag to resolver

* fix: move ff call to seperate function

---------

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* fix(vehicles-bulk-mileage): Fixes after testing review (#16295)

* fix: testing fixes v1

* fix: testing comments v2

* fix: better message

* fix: function name

* fix: duplicate loading

---------

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* feat(tests): New @island/testing/e2e library (#16287)

* Add @swc-node/register and @swc/core

* Add testing/e2e library

* update project.json for testing/e2e

* fix import for libTestingE2e

---------

Co-authored-by: Kristofer <kristofer@andes.is>
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* feat(parental-leave): ApplicationRights (#15901)

* feat(parental-leave): ApplicationRights

Added applicationRights to parental-leave when sending application. Since we are using a new way of calculating periods

* Fix days used by period calculation

* Tests for new periods

* rename function with proper camelCase

* Refactor: Made duplicate code into a function

* Make ApplicationRights nullable

* refactor: function instead of duplicate code

* remove console.log

* error handling for period data

* clientConfig nullable fix

* Fixes for calculation of months. And using clamp to get correct value of daysLeft

* Multiply amount of months by 30 for period calculation with month durations

* Fix old calculation of endDate with months

---------

Co-authored-by: hfhelgason <hfhelgason@deloitte.is>
Co-authored-by: veronikasif <54938148+veronikasif@users.noreply.github.com>
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* feat(passport-application): Updated readme (#16296)

* updated readme

* updated readme

* chore: nx format:write update dirty files

---------

Co-authored-by: andes-it <builders@andes.is>
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* fix(regulations-admin): date format signature, remove self affect, disclaimer text (#16288)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* fix(regulations-admin): No diff no addition in appendix (#16293)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* fix(web): Global alert banner - Handle null case (#16298)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* fix(web): Change custom syslumenn pages config for header (#16299)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* fix(j-s): Digital mailbox API (#16301)

* feat(j-s): Block create subpoena on staging and dev

* Update subpoena.service.ts

* fix(j-s): Fix mailbox API

* remove changes not meant for this branch

* Update subpoena.service.ts

* fix(j-s): reverting changes from other branch

* Update subpoena.response.ts

* Update subpoena.response.ts

* Update subpoena.response.ts

* Update subpoena.response.ts

---------

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* fix(signature-collection): Fix list reviewed toggle (#16300)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* chore(scripts): Stricter shell script checking (#16242)

* Set style level for shellcheck

* Linting & formatting scripts

* Remove _podman.sh script

* Format all scripts

* Add reviewdog/action-shfmt step

* Configure shfmt

* Merge from main

* Linting

* Move shfmt to before lint

* Remove reviewdog

* Allow external sources in shellcheck

* Use Reviewdog for shellcheck

* Set version for Reviewdog

---------

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* chore(new-primary-school): Update messages namespace (#16302)

Co-authored-by: veronikasif <54938148+veronikasif@users.noreply.github.com>
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* feat(driving-license): check if 65+ renewal is possible (#16292)

* check if 65 renewal is possible

* remove console log

* cleanup

* coderabbit tweaks

* coderabbit changes

* quick fix

* add type?

---------

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

* feat(service-portal): default defender and has chosen fields for subpoena (#16306)

* fix: def info and alert

* feat: add feature flag to resolver

* fix: move ff call to seperate function

* feat: add default choices ans has chosen + loading states

* fix: use type

* fix: undefined type issue

* fix: simplify check

* Update service setup for my pages infra

* chore: charts update dirty files

* Remove from infra

* undo rename

---------

Co-authored-by: albinagu <47886428+albinagu@users.noreply.github.com>
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
Co-authored-by: Ásdís Erna Guðmundsdóttir <disa@hugsmidjan.is>
Co-authored-by: Þorkell Máni Þorkelsson <wowthorkell@gmail.com>
Co-authored-by: Svanhildur Einarsdóttir <54863023+svanaeinars@users.noreply.github.com>
Co-authored-by: Kristofer <kristofer@andes.is>
Co-authored-by: helgifr <helgifreyr95@gmail.com>
Co-authored-by: hfhelgason <hfhelgason@deloitte.is>
Co-authored-by: veronikasif <54938148+veronikasif@users.noreply.github.com>
Co-authored-by: Rafn Árnason <rafnarnason@gmail.com>
Co-authored-by: andes-it <builders@andes.is>
Co-authored-by: Rúnar Vestmann <43557895+RunarVestmann@users.noreply.github.com>
Co-authored-by: mannipje <135017126+mannipje@users.noreply.github.com>
Co-authored-by: unakb <una@kolibri.is>
Co-authored-by: juni-haukur <158475136+juni-haukur@users.noreply.github.com>
Co-authored-by: birkirkristmunds <142495885+birkirkristmunds@users.noreply.github.com>
Co-authored-by: Kristján Albert <kal@juni.is>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this PR as soon as all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants