Skip to content

Conversation

@mtopo27
Copy link
Contributor

@mtopo27 mtopo27 commented Jan 12, 2026

endpoint works with either, but we're always parsing as the project ID, even though the compare build button takes you to {project-slug} route

@mtopo27 mtopo27 requested a review from a team as a code owner January 12, 2026 22:20
@linear
Copy link

linear bot commented Jan 12, 2026

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jan 12, 2026
? /^\d+$/.test(projectId)
? {project: projectId}
: {projectSlug: projectId}
: {}),
Copy link
Contributor

Choose a reason for hiding this comment

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

im not sure we should be deciding whether the value is the id or slug based off of its contents. I feel like it should instead be based on the context of the value

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

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants