Skip to content

Conversation

@mchang16-auth
Copy link
Contributor

Changes

  • Replaced all usage of "YOUR_API_IDENTIFIER" -> "{yourApiIdentifier}". Currently, if a user downloads the Auth0 Angular sample app without an API, the downloaded sample app has its audience value in auth_config.json set to
    "{yourApiIdentifier}". This is because "YOUR_API_IDENTIFIER" is no longer the default value, as it has been swapped with "{yourApiIdentifier}".

Supporting References

default value if you used the "Download Sample" feature of{" "}
<a href="https://auth0.com/docs/quickstart/spa/react">
the quickstart guide
</a>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Here I had to use the HTML characters for {}, as it was considering the brackets as JSX and causing the tests to fail.

@mchang16-auth mchang16-auth marked this pull request as ready for review February 27, 2025 22:49
!authConfig.domain ||
!authConfig.audience ||
authConfig.audience === "YOUR_API_IDENTIFIER"
["{yourApiIdentifier}", "{API_IDENTIFIER}"].includes(authConfig.audience)
Copy link

Choose a reason for hiding this comment

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

Can "{API_IDENTIFIER}" be passed as a default value? I am just wondering where this is coming from as "{yourApiIdentifier}" seems to be the default value.

Copy link

Choose a reason for hiding this comment

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

I just looked at some python sample apps and saw that they have "{API_IDENTIFIER}" as the default value for API_IDENTIFIER. Please disregard the above comment.

Copy link

@wdaimee wdaimee left a comment

Choose a reason for hiding this comment

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

LGTM

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