Repository navigation
docs: bring the README back in line with the code - #20
Merged
Merged
Conversation
A pass over the claims the last few changes made stale. No screenshots added; the existing ones stay as they are. - The leaderboard screenshot caption said it showed the viewer's own department. It was captured before the ranking was scoped, so the image is wider than what the app now returns. Saying so is better than a caption that quietly misdescribes the picture under it. - "Points and rewards — uploaders earn points from ratings" implied a stored balance. The total is the score the user's own notes have earned, computed where it is shown. - Rating rules — no self-rating, one vote per person — are now enforced by the security rules rather than only by the app, which is the part worth stating in a feature list. - Email verification moves from a gap to a decision. It is one call away and left open deliberately: the accounts here are test data, and a mandatory confirmation step would put a mailbox between a reviewer and the running app for nothing. - The pagination entry said the feed and leaderboard read every matching note and sorted in memory. Still true, but the leaderboard no longer reads the whole collection, and the createdAt normalisation the ordering depends on has already landed. The entry now says what is left rather than what was true two changes ago. - "Deploy the security rules" was a parenthetical. Now a step with the command in it, and a sentence on why it is not only about access: the rules are what verify the scoring, so an un-deployed project is either blocked or cheatable. - The rules-tests intro still cited `points` as an example of what only Firestore can enforce, and that field no longer exists. Verified: every in-page anchor resolves to a heading, and every relative link resolves to a file that exists. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
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 pass over the claims the last few changes made stale. No screenshots added — the existing ones stay as they are.
createdAtnormalisation the ordering depends on has landed. The entry now says what is left.pointsas an example of what only Firestore can enforceVerification
Every in-page anchor resolves to a heading, and every relative link resolves to a file that exists — checked mechanically, not by eye.
🤖 Generated with Claude Code