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

v3 - show salary for selected location, degree and examination year (web) #617

Merged
merged 3 commits into from
Sep 12, 2024

Conversation

mathiazom
Copy link
Contributor

@mathiazom mathiazom commented Sep 11, 2024

Further explanation is found here: #616

Replaces the hardcoded payscale with the location-based salary from Sanity.

Visual Overview (Image/Video)

No visual changes

Checklist

Please ensure that you’ve completed the following checkpoints before submitting your pull request:

  • Documentation: Relevant documentation has been added or updated (if applicable).
  • Testing: Have you tested your changes thoroughly?

Copy link

vercel bot commented Sep 11, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
variant-no ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 12, 2024 11:47am
variant-se-2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 12, 2024 11:47am

@mathiazom mathiazom changed the title v3 - show salary for selected location, degree and examination year v3 - show salary for selected location, degree and examination year (web) Sep 11, 2024
@@ -31,5 +38,6 @@ export interface CompensationsPage {
page: string;
slug: Slug;
benefitsByLocation: BenefitsByLocation[];
salaries: SalariesByLocation[];

Choose a reason for hiding this comment

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

I see we're doing salaries here, but benefitsByLocation above. Let's do either or

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That requires a breaking schema change, do we want to do it in this PR?

Choose a reason for hiding this comment

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

No not at all. We can do it in a cleanup?

Copy link

@christinaroise christinaroise left a comment

Choose a reason for hiding this comment

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

Nitpick comments, but overall good! 👏

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