-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
fix(bridge-ui): renamed configuredCustomToken to configuredCustomTokens #15905
fix(bridge-ui): renamed configuredCustomToken to configuredCustomTokens #15905
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@arularmstrong I have reopened the PR again as you were right after all. It seems due to some rebase the fix has been reverted. But the package has since moved to bridge-ui now, please rebase your PR to the latest main and then we can merge it.
02f83f1
to
f6ff7bf
Compare
f6ff7bf
to
5737418
Compare
@KorbinianK the PR is rebased with latest main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@arularmstrong You need to remove the incorrectly named ones as well please.
This PR addresses an inconsistency in the project's configuration file naming. The file in the config directory was originally named configuredCustomToken, while references elsewhere used configuredCustomTokens. To maintain consistency, I've renamed the file to configuredCustomTokens, aligning it with the Readme and other references.