generator: Generator doesn't pull template from private repo
Describe the bug
After upgrade to 1.6.0 version from 1.1.4, ag stopped to recognize npm configuration to use private repository
How to Reproduce
install @asyncapi/generator@1.6.0
configure NPM to use private repository using:
npm config set registry <path to registry>
try to generate code
ag ./server.yaml @repo/template --force-write --output ./out
see error - Error: 404 Not Found - GET https://registry.npmjs.org/<template in private repo> - Not found
install @asyncapi/generator@1.1.4
ag ./server.yaml @repo/template --force-write --output ./out
Done! ✨
Expected behavior
Ag should pull template from private repository
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 5
- Comments: 40 (24 by maintainers)
Commits related to this issue
- feat: :sparkles: added support for using current npm registry #538 — committed to rluvaton/generator by rluvaton 3 years ago
@aeworxet hey, thanks for reaching out about that topic. So yeah, I’d like to propose that we change this issue from Medium to Advanced. When
mediumlevel for this issue was assigned, I forgot to take into account advanced testing that will have o be added in a PR to test properly new functionality. I hope we have budget and can pay @AayushSaini101 at the end of the task foradvancedwork.Only 2 candidates can be considered for this issue, it is @AayushSaini101 and @princerajpoot20 Looking at bounty rules:
Although they did not have to open a PR (did it to quick), they proved he understands the scope and what he is signing up for. Hint for others in future, you can do the same without opening a PR, but just writing transparently in the comment what do you know about the issue
Both folks also made it super easy for me to quickly click on the link to confirm if they already had 3PR merged
Instead of going with some “coin flipping” solution, I decided to give this issue to @AayushSaini101 as he is not involved in any other AsyncAPI program (like mentorship)