feat: add t3app well-known playground routing #1800
Conversation
This file contains 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
🦋 Changeset detectedLatest commit: 1789089 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@yordis is attempting to deploy a commit to the t3-oss Team on Vercel. A member of the Team first needs to authorize it. |
yordis
force-pushed
the
add-t3app-wellknown-route
branch
from
cf0139a
to
1789089
Compare
yordis
requested review from
juliusmarminge,
nexxeln,
t3dotgg and
c-ehrlich
as code owners
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.
WIP: asking for feedback and general thoughts!
Rationale
Out of @t3dotgg streaming 2024-03-13 and the conversation around Storybook, one of the things I successfully applied across multiple projects is to leverage
.well-known/[namespace]to make cross-project collaboration that wouldn't conflict with application-level decisions.Introducing this route allows people to communicate intent and have a common place to do "Playground" work without worrying about
gitand stashing changes or making a mistake committing the changes. We all get to speak the same language and have a similar workflow.✅ Checklist
Changelog
[Short description of what has changed]
Screenshots
[Screenshots]
💯