Skip to content

Add invite-only registration mode - #1223

Open
korridor wants to merge 1 commit into
mainfrom
feature/registration_excl_invites
Open

Add invite-only registration mode#1223
korridor wants to merge 1 commit into
mainfrom
feature/registration_excl_invites

Conversation

@korridor

Copy link
Copy Markdown
Contributor

Support configurable on, invite-only, and off registration modes, including case-insensitive invitation checks and test coverage.

What does this PR do?

  • Fixes #XXXX (GitHub issue number)

Checklist (DO NOT REMOVE)

@codecov

codecov Bot commented Aug 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.38%. Comparing base (b2849ec) to head (303de49).

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1223      +/-   ##
============================================
+ Coverage     89.36%   89.38%   +0.02%     
- Complexity     2090     2100      +10     
============================================
  Files           283      284       +1     
  Lines         10117    10137      +20     
============================================
+ Hits           9041     9061      +20     
  Misses         1076     1076              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Support configurable on, invite-only, and off registration modes, including case-insensitive invitation checks and test coverage.
@korridor
korridor force-pushed the feature/registration_excl_invites branch from 789ec15 to 303de49 Compare August 25, 2026 16:20

public function test_invited_user_can_register_if_registration_is_invite_only(): void
{
Config::set('app.enable_registration', 'invite');

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

imo this should always test the same config not "invite" in one test and then "invite-only" in the other one

Comment thread .env.example
APP_DEBUG=true
APP_URL=https://solidtime.test
APP_FORCE_HTTPS=false
# Supported values: on/true, invite/invite-only, off/false

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

i'm fine with accepting both values as a fallback but i dont really see a reason for documenting 2 ways to do the same thing. i also think we should replace the ture/false examples and docs and have it consistently on/invite/off or on/invite-only/off everywhere.

Comment thread config/app.php
'force_https' => (bool) env('APP_FORCE_HTTPS', false),

'enable_registration' => (bool) env('APP_ENABLE_REGISTRATION', false),
'enable_registration' => env('APP_ENABLE_REGISTRATION', false),

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

i think this should be 'off' by default

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants