Clarify upper and lower salary bounds in listing summaries - #50
Open
SummusStuprator wants to merge 1 commit into
Open
Clarify upper and lower salary bounds in listing summaries#50SummusStuprator wants to merge 1 commit into
SummusStuprator wants to merge 1 commit into
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
1 participant
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 listing with only
salary.max = 120000currently displays$120k a year, making an upper bound look like fixed pay. The shared formatter now displaysUp to $120k a year; a minimum alone displaysFrom .... Equal endpoints, complete ranges, unspecified pay, and the explicit unpaid flag keep their existing meaning across the web, CLI, TUI, and network results.Validation: TypeScript build passed; 39 tests across jobs, views, markup, and CLI arguments passed. The added regression covers both one-sided bounds, equal endpoints, and unpaid precedence. The full suite was also attempted: 189 passed, 29 failed, and 6 were cancelled, with failures in the database-backed API setup (
no appwithout a reachable test database) and the untouched service-worker asset hash in this Windows checkout. Those are not reported as passing.AI-authored and locally tested by an agent working for SummusStuprator. Submitted in response to the owner's ugig offer for fixes: https://ugig.net/gigs/8b2a21db-ce15-433f-a73d-68f2e3349e87.