Improve the wellposed entry: description and site link - #123
suraj-phanindra wants to merge 1 commit into
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe Wellposed project entry now links to its npm package. Its description now covers offline checks for missing none-of-the-above options and broken state paths, and Jev's role in deciding what structure cannot. ChangesWellposed listing
Estimated code review effort: 1 (Trivial) | ~3 minutes Suggested reviewers: Merge Risk: ⚪ Minimal · up to This is a metadata-only listing update; no material merge risk is evident. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Landed on main as 24fceb2 with you as the commit author, now live on https://awesomejev.com. Closing rather than merging because every PR appends to the same data file and they conflict with each other; landing directly keeps your authorship. Thanks! |
I maintain this project. Nightly discovery picked it up in 43cb753, which scraped my GitHub repo description — that line is a tagline rather than a description of what the tool does, so it does not meet the bar in CONTRIBUTING ("one sentence, plain language, what it does and where Jev fits").
Two changes to the existing entry, nothing added or removed:
description— says what it checks and where Jev is used. 167 chars, near the 114-char median foragents.site— the npm page, since it installs withnpx wellposed lint request.json.For context: it lints a Jev request before you send it. Offline structural rules first, with no API key — a Choice with no none-of-the-above option, backticked state paths that do not resolve, criteria in the wrong shape for the primitive. Then Jev itself for what structure cannot settle, such as whether "none of these" is actually reachable for a given option set. Both layers ship labelled corpora, so
npm run evalandnpm run eval:semanticreproduce the numbers rather than asserting them.npm run validatepasses at 1081 entries. Onlydata/projects.jsonchanged;stars,language,pushedandcreatedare untouched so the nightly refresh keeps managing them. Checkedrefresh.mjs:36-37— both fields I set are only auto-filled when empty, so this will not be overwritten.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by CodeRabbit