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(tests): New @island/testing/e2e library #16287

Merged
merged 6 commits into from
Oct 7, 2024

Conversation

svanaeinars
Copy link
Member

@svanaeinars svanaeinars commented Oct 7, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a new library for end-to-end testing, including configuration files for ESLint, Jest, and TypeScript.
    • Added a utility function that returns a specific string value.
    • Created a README file with instructions for running unit tests.
    • Enhanced module resolution for end-to-end testing components.
  • Documentation

    • New README file added to provide an overview of the end-to-end testing library.
  • Tests

    • Implemented a new test suite to verify the functionality of the library.

@svanaeinars svanaeinars requested a review from a team as a code owner October 7, 2024 09:45
Copy link
Contributor

coderabbitai bot commented Oct 7, 2024

Walkthrough

This pull request introduces several new configuration files and a README for the libs/testing/e2e directory. It includes an ESLint configuration that extends from a base configuration, a Jest configuration for end-to-end testing, and multiple TypeScript configuration files. A project configuration file is also added, defining targets for linting and testing. Additionally, a new utility function and its corresponding test suite are introduced, along with re-exports for easier module access.

Changes

File Path Change Summary
libs/testing/e2e/.eslintrc.json New ESLint configuration file created, extending base settings and defining file type overrides.
libs/testing/e2e/README.md New README file created, providing an overview and instructions for running unit tests.
libs/testing/e2e/jest.config.ts New Jest configuration file created, specifying settings for end-to-end tests.
libs/testing/e2e/project.json New project configuration file created, defining metadata and targets for linting and testing.
libs/testing/e2e/src/index.ts Export statement added to re-export all entities from ./lib/libs/testing/e2e.
libs/testing/e2e/src/lib/libs/testing/e2e.spec.ts New test suite created to verify functionality of the libsTestingE2e module.
libs/testing/e2e/src/lib/libs/testing/e2e.ts New function libsTestingE2e added, returning a string literal.
libs/testing/e2e/tsconfig.json New TypeScript configuration file created, extending from a base configuration.
libs/testing/e2e/tsconfig.lib.json New TypeScript configuration file created for library settings, specifying output and exclusions.
libs/testing/e2e/tsconfig.spec.json New TypeScript configuration file created for testing purposes, specifying output and includes.
tsconfig.base.json New path mapping added for @island.is/testing/e2e to resolve imports to the specified source.

Possibly related PRs

Suggested labels

automerge

Suggested reviewers

  • lodmfjord
  • oddsson
  • Toti91
  • eirikurn

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

🧹 Outside diff range and nitpick comments (6)
libs/testing/e2e/src/lib/libs/testing/e2e.ts (1)

1-3: Good implementation, but consider enhancing documentation and purpose.

The function is well-implemented with proper TypeScript usage. The named export is favorable for tree-shaking. However, the purpose of this function is not immediately clear.

Consider adding a JSDoc comment to explain the function's purpose and usage. For example:

/**
 * Returns the identifier for the e2e testing library.
 * This can be used for logging, configuration, or other identification purposes.
 * @returns {string} The identifier string for the e2e testing library.
 */
export function libsTestingE2e(): string {
  return 'libs/testing/e2e'
}

If this function is intended to provide a constant identifier, consider using a named constant instead:

export const E2E_LIBRARY_IDENTIFIER = 'libs/testing/e2e'

This approach would be more efficient and clearer in its intent.

libs/testing/e2e/src/lib/libs/testing/e2e.spec.ts (1)

1-7: Test suite structure looks good, but consider expanding test coverage.

The test suite is correctly structured using Jest's describe and it functions, and the import statement is properly defined. However, there's room for improvement:

  1. Consider adding more test cases to cover different scenarios and edge cases of the libsTestingE2e function.
  2. Add type annotations to improve TypeScript usage, especially for function parameters and return types.

Here's an example of how you could expand the test suite:

import { libsTestingE2e } from './libs/testing/e2e';

describe('libsTestingE2e', () => {
  it('should return the correct string', () => {
    expect(libsTestingE2e()).toEqual('libs/testing/e2e');
  });

  it('should always return a string', () => {
    const result: string = libsTestingE2e();
    expect(typeof result).toBe('string');
  });

  // Add more test cases as needed
});
libs/testing/e2e/tsconfig.spec.json (1)

8-13: LGTM: Comprehensive inclusion of test files.

The include section is well-configured:

  • It includes the Jest configuration file, which is necessary for the test setup.
  • The patterns for test files are comprehensive, covering both .test.ts and .spec.ts conventions.
  • Including .d.ts files ensures that type declaration files are properly processed.

This configuration supports TypeScript usage for testing, aligning with the coding guidelines for the libs directory.

For improved clarity, consider combining the test file patterns:

  "include": [
    "jest.config.ts",
-   "src/**/*.test.ts",
-   "src/**/*.spec.ts",
-   "src/**/*.d.ts"
+   "src/**/*.{test,spec,d}.ts"
  ]

This change doesn't affect functionality but makes the configuration more concise.

libs/testing/e2e/project.json (3)

7-13: LGTM: Lint configuration is properly set up.

The lint target is well-configured using ESLint for TypeScript files. However, consider adding .tsx files to the lint patterns for broader coverage:

- "lintFilePatterns": ["libs/testing/e2e/**/*.ts"]
+ "lintFilePatterns": ["libs/testing/e2e/**/*.{ts,tsx}"]

This change ensures that any potential JSX/TSX files in the e2e tests are also linted.


14-27: Test configuration looks good, but consider enforcing test presence.

The test target is well-configured using Jest, with appropriate settings for CI and code coverage. However, for an e2e testing library, it might be beneficial to ensure that tests are always present:

- "passWithNoTests": true
+ "passWithNoTests": false

This change would cause the test run to fail if no tests are found, encouraging developers to always include tests in this critical library.


29-29: Consider adding relevant tags to the project.

The tags array is currently empty. Adding relevant tags can improve project organization and discoverability within your monorepo. Consider adding tags such as:

- "tags": []
+ "tags": ["scope:e2e", "type:testing", "target:browser"]

These tags would clearly indicate the purpose and scope of this library, making it easier to manage and locate within your project structure.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

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

📒 Files selected for processing (11)
  • libs/testing/e2e/.eslintrc.json (1 hunks)
  • libs/testing/e2e/README.md (1 hunks)
  • libs/testing/e2e/jest.config.ts (1 hunks)
  • libs/testing/e2e/project.json (1 hunks)
  • libs/testing/e2e/src/index.ts (1 hunks)
  • libs/testing/e2e/src/lib/libs/testing/e2e.spec.ts (1 hunks)
  • libs/testing/e2e/src/lib/libs/testing/e2e.ts (1 hunks)
  • libs/testing/e2e/tsconfig.json (1 hunks)
  • libs/testing/e2e/tsconfig.lib.json (1 hunks)
  • libs/testing/e2e/tsconfig.spec.json (1 hunks)
  • tsconfig.base.json (1 hunks)
✅ Files skipped from review due to trivial changes (6)
  • libs/testing/e2e/.eslintrc.json
  • libs/testing/e2e/README.md
  • libs/testing/e2e/jest.config.ts
  • libs/testing/e2e/src/index.ts
  • libs/testing/e2e/tsconfig.json
  • libs/testing/e2e/tsconfig.lib.json
🧰 Additional context used
📓 Path-based instructions (4)
libs/testing/e2e/project.json (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/testing/e2e/src/lib/libs/testing/e2e.spec.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/testing/e2e/src/lib/libs/testing/e2e.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/testing/e2e/tsconfig.spec.json (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 (5)
libs/testing/e2e/tsconfig.spec.json (3)

2-2: LGTM: Proper extension from base configuration.

Extending from a base tsconfig.json is a good practice. It promotes consistency and reduces configuration duplication across the project.


3-7: LGTM: Compiler options are well-configured for testing.

The compiler options are appropriately set for a testing environment:

  • The outDir setting organizes compiled files efficiently.
  • Using "commonjs" as the module system is suitable for Node.js environments, which is typical for testing.
  • Including types for Jest and Node.js ensures proper type checking in test files.

These settings align with the coding guidelines for effective bundling practices in the libs directory.


1-14: Overall assessment: Well-configured TypeScript setup for e2e testing.

This tsconfig.spec.json file is well-structured and follows good practices for TypeScript configuration in a testing context. It aligns with the coding guidelines for files in the libs directory:

  1. It supports reusability across different NextJS apps by providing a consistent testing setup.
  2. It properly uses TypeScript for testing purposes, including necessary type definitions.
  3. The configuration supports effective tree-shaking and bundling practices through appropriate compiler options.

The file successfully sets up a TypeScript environment tailored for end-to-end testing, which will contribute to maintaining code quality and type safety in the testing process.

libs/testing/e2e/project.json (1)

1-5: LGTM: Project metadata is well-defined.

The project metadata is correctly configured for an e2e testing library in an Nx workspace. The project name, schema reference, sourceRoot, and projectType are all appropriately set.

tsconfig.base.json (1)

1115-1115: LGTM: New path mapping for e2e testing library added.

The addition of the path mapping for "@island.is/testing/e2e" is consistent with the PR objectives and enhances the module resolution capabilities for end-to-end testing components.

Let's verify if there are any other files that might need updates due to this new path mapping:

✅ Verification successful

Action Required: Correct the search command to properly target TypeScript and JavaScript files.

The previous search failed because typescript is not a recognized file type in rg. Please run the following script to search within .ts and .tsx files:


Verified: No additional files require updates due to the new path mapping for "@island.is/testing/e2e".

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for files that might need updates due to the new path mapping
rg --type typescript --type javascript -i '@island.is/testing/e2e'

Length of output: 101


Script:

#!/bin/bash
# Search for files that might need updates due to the new path mapping
rg -g '*.ts' -g '*.tsx' -i '@island.is/testing/e2e'

Length of output: 51

@svanaeinars svanaeinars changed the title Feat/add testing e2e library feat: add testing e2e library Oct 7, 2024
Copy link

codecov bot commented Oct 7, 2024

Codecov Report

Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 36.87%. Comparing base (eeabe7f) to head (64c0333).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
libs/testing/e2e/src/index.ts 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #16287      +/-   ##
==========================================
- Coverage   36.87%   36.87%   -0.01%     
==========================================
  Files        6796     6798       +2     
  Lines      140565   140568       +3     
  Branches    39979    39979              
==========================================
  Hits        51836    51836              
- Misses      88729    88732       +3     
Flag Coverage Δ
air-discount-scheme-backend 54.23% <ø> (ø)
air-discount-scheme-web 0.00% <ø> (ø)
api 3.37% <ø> (ø)
api-domains-air-discount-scheme 36.98% <ø> (ø)
api-domains-assets 26.71% <ø> (ø)
api-domains-auth-admin 48.77% <ø> (ø)
api-domains-communications 39.92% <ø> (ø)
api-domains-criminal-record 47.96% <ø> (ø)
api-domains-driving-license 44.50% <ø> (ø)
api-domains-education 31.44% <ø> (ø)
api-domains-health-insurance 34.83% <ø> (ø)
api-domains-mortgage-certificate 35.74% <ø> (ø)
api-domains-payment-schedule 41.25% <ø> (ø)
application-api-files 57.94% <ø> (ø)
application-core 71.29% <ø> (ø)
application-system-api 41.58% <ø> (ø)
application-template-api-modules 24.32% <ø> (-0.02%) ⬇️
application-templates-accident-notification 29.44% <ø> (ø)
application-templates-car-recycling 3.12% <ø> (ø)
application-templates-criminal-record 26.63% <ø> (ø)
application-templates-driving-license 18.63% <ø> (ø)
application-templates-estate 12.32% <ø> (ø)
application-templates-example-payment 25.41% <ø> (ø)
application-templates-financial-aid 14.34% <ø> (ø)
application-templates-general-petition 23.68% <ø> (ø)
application-templates-health-insurance 26.62% <ø> (ø)
application-templates-inheritance-report 6.45% <ø> (ø)
application-templates-marriage-conditions 15.23% <ø> (ø)
application-templates-mortgage-certificate 43.96% <ø> (ø)
application-templates-parental-leave 30.15% <ø> (ø)
application-types 6.71% <ø> (ø)
application-ui-components 1.28% <ø> (ø)
application-ui-shell 21.27% <ø> (ø)
clients-charge-fjs-v2 24.11% <ø> (ø)
clients-driving-license 40.77% <ø> (ø)
clients-driving-license-book 43.93% <ø> (ø)
clients-financial-statements-inao 49.29% <ø> (ø)
clients-license-client 1.83% <ø> (ø)
clients-regulations 42.76% <ø> (ø)
clients-rsk-company-registry 29.76% <ø> (ø)
clients-rsk-personal-tax-return 38.00% <ø> (ø)
clients-smartsolutions 12.77% <ø> (ø)
clients-syslumenn 49.67% <ø> (ø)
cms 0.43% <ø> (ø)
cms-translations 39.05% <ø> (ø)
dokobit-signing 63.29% <ø> (ø)
download-service 44.11% <ø> (ø)
email-service 61.05% <ø> (ø)
feature-flags 91.04% <ø> (ø)
file-storage 53.59% <ø> (ø)
financial-aid-backend 56.54% <ø> (ø)
judicial-system-api 18.22% <ø> (ø)
judicial-system-audit-trail 69.27% <ø> (ø)
judicial-system-backend 55.19% <ø> (ø)
judicial-system-message 67.18% <ø> (ø)
judicial-system-message-handler 48.26% <ø> (ø)
judicial-system-scheduler 69.39% <ø> (ø)
license-api 42.63% <ø> (+0.07%) ⬆️
nest-config 78.38% <ø> (ø)
nest-feature-flags 52.02% <ø> (ø)
nova-sms 62.65% <ø> (ø)
portals-admin-regulations-admin 1.88% <ø> (ø)
portals-core 16.15% <ø> (ø)
services-auth-admin-api 51.99% <ø> (ø)
services-auth-delegation-api 57.87% <ø> (ø)
services-auth-ids-api 51.87% <ø> (-0.01%) ⬇️
services-auth-personal-representative 45.55% <ø> (+0.02%) ⬆️
services-auth-personal-representative-public 41.64% <ø> (ø)
services-auth-public-api 49.37% <ø> (-0.02%) ⬇️
services-endorsements-api 55.23% <ø> (ø)
services-sessions 65.81% <ø> (ø)
services-university-gateway 48.57% <ø> (ø)
services-user-notification 47.05% <ø> (-0.03%) ⬇️
services-user-profile 62.37% <ø> (ø)
testing-e2e 66.66% <66.66%> (?)
web 1.83% <ø> (ø)

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

Files with missing lines Coverage Δ
libs/testing/e2e/src/lib/libs/testing/e2e.ts 100.00% <100.00%> (ø)
libs/testing/e2e/src/index.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 eeabe7f...64c0333. Read the comment docs.

@svanaeinars svanaeinars changed the title feat: add testing e2e library feat(tests): add testing e2e library Oct 7, 2024
@svanaeinars svanaeinars changed the title feat(tests): add testing e2e library feat(tests): New @island/testing/e2e library Oct 7, 2024
@svanaeinars svanaeinars added the automerge Merge this PR as soon as all checks pass label Oct 7, 2024
@datadog-island-is
Copy link

Datadog Report

All test runs bf5ba7f 🔗

70 Total Test Services: 0 Failed, 68 Passed
➡️ Test Sessions change in coverage: 199 no change

Test Services
This report shows up to 10 services
Service Name Failed Known Flaky New Flaky Passed Skipped Total Time Code Coverage Change Test Service View
air-discount-scheme-backend 0 0 0 81 0 30.87s N/A Link
air-discount-scheme-web 0 0 0 2 0 8.48s 1 no change Link
api 0 0 0 4 0 2.68s N/A Link
api-domains-air-discount-scheme 0 0 0 6 0 18.51s 1 no change Link
api-domains-assets 0 0 0 3 0 12.03s 1 no change Link
api-domains-auth-admin 0 0 0 18 0 13.48s 1 no change Link
api-domains-communications 0 0 0 5 0 31.46s 1 no change Link
api-domains-criminal-record 0 0 0 5 0 9.65s 1 no change Link
api-domains-driving-license 0 0 0 23 0 28.92s 1 no change Link
api-domains-education 0 0 0 8 0 19.65s 1 no change Link

@kodiakhq kodiakhq bot merged commit 618f23f into main Oct 7, 2024
200 checks passed
@kodiakhq kodiakhq bot deleted the feat/add-testing-e2e-library branch October 7, 2024 16:25
thordurhhh pushed a commit that referenced this pull request Oct 8, 2024
* 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>
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.

3 participants