这是indexloc提供的服务,不要输入任何密码
Skip to content

Set a fallback for the user's name when running turbo link #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 9, 2021

Conversation

dglsparsons
Copy link
Contributor

@dglsparsons dglsparsons commented Dec 9, 2021

This PR adds a fallback for a User's name to their username. Name is an optional field in Vercel. My user, for example, does not have a name (I don't know how or why).

This then makes it impossible to set up turbo link to a personal workspace.
e.g.

Screenshot 2021-12-09 at 16 31 42

Selecting the empty option prompts: X Sorry, your reply was invalid: Value is required

Post change:
Screenshot 2021-12-09 at 16 34 15

@vercel
Copy link

vercel bot commented Dec 9, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/vercel/turbo-site/HFcP6LPPNAA7yfwBTFJ5Zkbn79Jc
✅ Preview: https://turbo-site-git-set-user-name-fallback.vercel.sh

@dglsparsons dglsparsons changed the title Set a fallback for the user's name Set a fallback for the user's name when running turbo link Dec 9, 2021
@jaredpalmer jaredpalmer merged commit f107f31 into main Dec 9, 2021
@jaredpalmer jaredpalmer deleted the set-user-name-fallback branch December 9, 2021 16:44
sokra pushed a commit that referenced this pull request Oct 25, 2022
Relocate troubleshooting tip for node-canvas
sokra pushed a commit that referenced this pull request Oct 25, 2022
Note that this doesn't completely close out
[#54](vercel/web-tooling-internal#54) as the
[tailwindcss config is
optional](https://tailwindcss.com/docs/configuration). I'm digging
deeper at additional ways to detect tailwind, but putting this up since
it's a strict improvement.

```
olszewski@chriss-mbp next-dev % cargo run -p next-dev -- /tmp/with-tailwindcss-app
   Compiling next-dev v0.1.0 (/Users/olszewski/code/vercel/the-three-body/crates/next-dev)
    Finished dev [unoptimized + debuginfo] target(s) in 11.61s
     Running `/Users/olszewski/code/vercel/the-three-body/target/debug/next-dev /tmp/with-tailwindcss-app`
server listening on: http://localhost:3000
error [unimplemented]
  /private/tmp/with-tailwindcss-app/next.config.js
    Feature not yet supported
    Handling the file `next.config.js` is currently unimplemented

  /private/tmp/with-tailwindcss-app/postcss.config.js
    Feature not yet supported
    Handling the file `postcss.config.js` is currently unimplemented

  /private/tmp/with-tailwindcss-app/tailwind.config.js
    Feature not yet supported
    Handling the file `tailwind.config.js` is currently unimplemented

[200] / (3045ms)
initial compilation 3468ms (3044ms task execution, 48380 tasks)
updated in 874ms (8990 tasks)
```
jridgewell pushed a commit to vercel/next.js that referenced this pull request Mar 10, 2023
)

Note that this doesn't completely close out
[vercel/turborepo#54](vercel/web-tooling-internal#54) as the
[tailwindcss config is
optional](https://tailwindcss.com/docs/configuration). I'm digging
deeper at additional ways to detect tailwind, but putting this up since
it's a strict improvement.

```
olszewski@chriss-mbp next-dev % cargo run -p next-dev -- /tmp/with-tailwindcss-app
   Compiling next-dev v0.1.0 (/Users/olszewski/code/vercel/the-three-body/crates/next-dev)
    Finished dev [unoptimized + debuginfo] target(s) in 11.61s
     Running `/Users/olszewski/code/vercel/the-three-body/target/debug/next-dev /tmp/with-tailwindcss-app`
server listening on: http://localhost:3000
error [unimplemented]
  /private/tmp/with-tailwindcss-app/next.config.js
    Feature not yet supported
    Handling the file `next.config.js` is currently unimplemented

  /private/tmp/with-tailwindcss-app/postcss.config.js
    Feature not yet supported
    Handling the file `postcss.config.js` is currently unimplemented

  /private/tmp/with-tailwindcss-app/tailwind.config.js
    Feature not yet supported
    Handling the file `tailwind.config.js` is currently unimplemented

[200] / (3045ms)
initial compilation 3468ms (3044ms task execution, 48380 tasks)
updated in 874ms (8990 tasks)
```
sokra pushed a commit to vercel/next.js that referenced this pull request Mar 13, 2023
)

Note that this doesn't completely close out
[vercel/turborepo#54](vercel/web-tooling-internal#54) as the
[tailwindcss config is
optional](https://tailwindcss.com/docs/configuration). I'm digging
deeper at additional ways to detect tailwind, but putting this up since
it's a strict improvement.

```
olszewski@chriss-mbp next-dev % cargo run -p next-dev -- /tmp/with-tailwindcss-app
   Compiling next-dev v0.1.0 (/Users/olszewski/code/vercel/the-three-body/crates/next-dev)
    Finished dev [unoptimized + debuginfo] target(s) in 11.61s
     Running `/Users/olszewski/code/vercel/the-three-body/target/debug/next-dev /tmp/with-tailwindcss-app`
server listening on: http://localhost:3000
error [unimplemented]
  /private/tmp/with-tailwindcss-app/next.config.js
    Feature not yet supported
    Handling the file `next.config.js` is currently unimplemented

  /private/tmp/with-tailwindcss-app/postcss.config.js
    Feature not yet supported
    Handling the file `postcss.config.js` is currently unimplemented

  /private/tmp/with-tailwindcss-app/tailwind.config.js
    Feature not yet supported
    Handling the file `tailwind.config.js` is currently unimplemented

[200] / (3045ms)
initial compilation 3468ms (3044ms task execution, 48380 tasks)
updated in 874ms (8990 tasks)
```
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.

3 participants