Closed iamrajjoshi closed 1 week ago
This pull request was deployed and Sentry observed the following issues:
/api/0/organizations/{organization_slug}/releas...
View Issue/api/0/projects/{organization_slug}/{project_id...
View IssueDid you find this useful? React with a 👍 or 👎
We are adding support for
{resource}.id_or_slug
support in our API path parameters. Currently our api gateway relied on "organization_slug" existing in the path parameter.This PR adds support for
organization_id_or_slug
existing in path parameter, so when we go change all our apis from organization_slug to organization_id_or_slug, we can still proxy correctly.I also a test for this. Let me know if I am missing something.
Note:
id_or_slug_path_params_enabled
is a wrapper for a couple of options that are used to rollout the API changes.