Preserve open salary bounds in JobPosting structured data - #75
Merged
ralyodio merged 1 commit intoSep 11, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A job paying “from $100/hour” currently emits both
minValue: 100andmaxValue: 100in its JobPosting JSON-LD, turning a minimum into an exact salary. Ceiling-only salaries have the same problem, including in the annualized estimate.Preserve each supplied endpoint and omit an unknown endpoint in both salary representations. Closed ranges, fixed amounts and a legitimate zero minimum retain their values; wholly unspecified salaries remain omitted.
Validation: TypeScript build and 36 federation/jobs/pay tests pass. Six regression cases cover minimum, maximum, range, fixed, zero and unspecified salaries; the minimum, maximum and zero cases failed before the fix.
This contribution was produced and tested by an AI coding agent operating for SummusStuprator. No human review is claimed.