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

Iterate the pre-check to include an interoperability check #239

Draft
wants to merge 67 commits into
base: main
Choose a base branch
from

Conversation

mpanne
Copy link
Contributor

@mpanne mpanne commented Dec 16, 2024

  • Add questions regarding EU interoperability
  • Update pre-check landing and result pages to include information about interoperability
  • Add page with general information prior to pre-check questions
  • Update content of some pre-check pages

@mpanne mpanne marked this pull request as draft December 16, 2024 10:17
@mpanne mpanne force-pushed the feature_interoperability-pre-check branch 6 times, most recently from 1ce6d24 to 9c30b6d Compare December 19, 2024 14:59
Copy link
Contributor

@HendrikSchmidt HendrikSchmidt left a comment

Choose a reason for hiding this comment

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

Hey, great work! I left a mix of nitpicks and medium proposals, lmk if you need any clarification.

With the possible refactorings and maybe pulling some components out of ResultPage (ReasoningList first and foremost probably), I am starting to think we might get away without the three files and could still merge route.tsx and ResultPage. Interested in your thoughts!

@@ -26,7 +26,6 @@ jobs:

build-and-push-image:
needs: [check-and-test-shared]
if: ${{ github.ref == 'refs/heads/main' }}
Copy link
Contributor

Choose a reason for hiding this comment

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

Doesn't this lead to PR branches (e.g. by dependabot) being deployed, too?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, that's the whole point of it. To have the PR branches built so that we can use the published images for staging deployment (manually atm). That way we could also test a dependabot PR on staging. Whereas I agree that this is more an unwanted side effect than a feature. Do you see a problem with this approach?

}
>
<Container backgroundColor="white" additionalClassNames="rounded-b-lg">
<div className="pb-40 border-solid border-0 border-b-2 border-gray-400 last:border-0 last:pb-0">
Copy link
Contributor

Choose a reason for hiding this comment

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

border-0 seems unnecessary here

@mpanne mpanne force-pushed the feature_interoperability-pre-check branch from 8a286be to 181d79f Compare January 6, 2025 10:48
@mpanne mpanne force-pushed the feature_interoperability-pre-check branch from 5a27cbc to bd7665d Compare January 6, 2025 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants