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

team_id should not be computed #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
Oct 24, 2023
Merged

team_id should not be computed #137

merged 1 commit into from
Oct 24, 2023

Conversation

dglsparsons
Copy link
Collaborator

Team IDs are optionally set on a per-resource basis. However, when omitted, they should not be set as 'computed', because they can never be anything other than Null/Unknown. Computed makes them show as unknown, expecting the value to later be set.

This causes a weird churn when creating resources under a personal Vercel account.

Closes #136

Team IDs are optionally set on a per-resource basis.
However, when omitted, they should not be set as 'computed', because
they can never be anything other than Null/Unknown. Computed makes them
show as unknown, expecting the value to later be set.

This causes a weird churn when creating resources under a personal
Vercel account.

Closes #136
@dglsparsons dglsparsons requested a review from ecklf October 24, 2023 11:26
@dglsparsons dglsparsons merged commit 42e9671 into main Oct 24, 2023
@dglsparsons dglsparsons deleted the non-computed-team-id branch October 24, 2023 12:11
dglsparsons added a commit that referenced this pull request Oct 24, 2023
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.

Any configuration change will recreate the vercel project
2 participants