We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Take a look at the issue described here: #3031
Users occasionally have to suffix go-getter URLs in Catalog/Scaffold with //. in order to have them parsed correctly.
//.
It's likely related to how we're parsing the URLs in the actions.
We should improve test coverage so that users don't hit weird edge cases.
Users should be able to use any valid go-getter URL for the Catalog and Scaffold commands.
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
go-getter
No branches or pull requests
Describe the bug
Take a look at the issue described here:
#3031
Users occasionally have to suffix go-getter URLs in Catalog/Scaffold with
//.
in order to have them parsed correctly.It's likely related to how we're parsing the URLs in the actions.
We should improve test coverage so that users don't hit weird edge cases.
Expected behavior
Users should be able to use any valid go-getter URL for the Catalog and Scaffold commands.
Nice to haves
Versions
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: