Skip to content

Conversation

@ch1kim0n1
Copy link
Member

@ch1kim0n1 ch1kim0n1 commented Jan 1, 2026

Added conditional pages for:

  • page not found (404)
  • error page (and a lil guide on what to do)
  • Maintence page
  • loading page (just in case)
  • status page to show if meteormate is up

All of the pages follow MeteorMate's web design.

Also added rate limiting on registration & login in order to prevent system overloads by repeatedly inputting wrong information. (assuming its done on purpose after 10th time)

@ch1kim0n1 ch1kim0n1 requested a review from ryanpolasky January 1, 2026 19:44
@ch1kim0n1 ch1kim0n1 changed the title Add conditional pages: 404, loading, error, maintenance, and rate limiting [FEATURE] Add conditional pages: 404, loading, error, maintenance, and rate limiting Jan 1, 2026
@ryanpolasky ryanpolasky self-assigned this Jan 2, 2026
@ryanpolasky ryanpolasky added Design Design-related changes Code Quality Refactors & fixed related to code quality. labels Jan 2, 2026
@ryanpolasky ryanpolasky changed the title [FEATURE] Add conditional pages: 404, loading, error, maintenance, and rate limiting feat: Add conditional pages (404, loading, error, maintenance, rate limiting) Jan 2, 2026
@ryanpolasky ryanpolasky added the Type: Feature Request New feature or request label Jan 2, 2026
Copy link
Contributor

@ryanpolasky ryanpolasky left a comment

Choose a reason for hiding this comment

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

Just a couple changes to take a look at here. If you can get these few things adjusted we can get this merged asap :) Great work as always!

@ch1kim0n1 ch1kim0n1 requested a review from ryanpolasky January 5, 2026 02:14
@ch1kim0n1
Copy link
Member Author

Changes that were suggested were made!

@ryanpolasky
Copy link
Contributor

@ch1kim0n1 I noticed we now have auth error mapping both in authErrors.ts (from your first PR) and again in sanitizeErrorMessage inside the error boundary (in this PR). They look like they’re trying to solve the same problem but in different layers. Might be worth centralizing this so we don’t end up with two diverging mappings over time. Do you maybe want to go ahead & rebase w/ main and centralize the two? Otherwise though, all your fixes look great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Code Quality Refactors & fixed related to code quality. Design Design-related changes Type: Feature Request New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants