Add Teams variant to the API starter kit#80
Open
WendellAdriel wants to merge 18 commits into
Open
Conversation
41c3dcd to
c73b048
Compare
59ea28f to
b5b22b7
Compare
pushpak1300
reviewed
Apr 28, 2026
pushpak1300
reviewed
Apr 28, 2026
pushpak1300
reviewed
Apr 28, 2026
pushpak1300
requested changes
Apr 28, 2026
pushpak1300
left a comment
Member
There was a problem hiding this comment.
Having a test to check test_non_member_cannot_access_team will be great.
21fbabe to
c45c6d6
Compare
a566d04 to
82249c0
Compare
|
I was wondering if this PR is close enough to final to already base a new project on? |
dffbd39 to
153376d
Compare
0d8fc7f to
f871ec3
Compare
a9f93c2 to
b4554a3
Compare
|
So cool! Will this go live together with the parent PR (API starter kit) or will it come later? |
Member
Author
|
@RasmusPJustesen the idea is to release together with the base API starter kit. |
b4554a3 to
c060ddc
Compare
BuildCommand, StarterKit enum, kit-manifest, check-kits, and kit-helpers updated to handle the new API kit. GitHub Actions workflows include the API variant in test and push matrices. README, CLAUDE.md, AGENTS.md, and SKILL.md reflect the new variant count (22) and --api flag.
Move verification.verify back outside auth:sanctum so signed links work without a bearer token. Block self-role changes in TeamMemberController so an owner cannot demote themselves. Authenticate TeamMemberTest through Sanctum tokens and assert ownership stability on every update and remove path. Generate the personal-team slug from the overridden name in UserFactory so fixtures stay consistent.
Make TeamMemberController@destroy 404 when the targeted user has no
membership instead of silently returning 204. Move invitation accept
to GET /invitations/{invitation}/accept under signed middleware with
a 3-day TTL, validate state inline, and resolve the user by
case-insensitive email match. Add a kit-local TeamInvitation
notification override that emits the signed URL via
URL::temporarySignedRoute, leaving Inertia/Livewire variants on the
original GET link. Drop the manual Str::slug build in UserFactory's
afterCreating block to match the Fortify and WorkOS variant
convention.
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.
The API starter kit now ships a Teams variant so API-first apps get the same team management feature set (members, invitations, permissions, roles) that the Inertia and Livewire Teams kits already offer.
A new
API/Teamslayer sits on top ofShared/Teams/Base, skipping the Fortify layer in favour of its ownRegisterController, User model, andHasTeamstrait that omit the session-based "current team" concept — stateless APIs pass team context per request instead. The five Team form requests moved fromInertia/Teams/Baseup toShared/Teams/Baseso both stacks reuse them. Orchestrator, manifest, and workflows were wired to build and CI-check the newapi-teamsvariant.