feat: implement 'new glee' command

[peter-rr]

Related issue(s)
Resolves #184

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

No Coverage information
55.7% Duplication

[fmvilas]

This is going great! 💪

I left a few suggestions. Also, if I recall correctly, the asyncapi new glee command should have an alias called asyncapi new project. You should add that by creating the project.ts file in the same directory. It can simply be a file that imports the glee.ts and exports everything it's exporting (same as with new/index.ts, which is an alias of new/file.ts). Also, make sure console messages suggest asyncapi new project or asyncapi new glee, depending on which one has been used.

Keep up the great work 🙌

[fmvilas]

Left some comments but it's already looking good to get out of the Draft PR stage 🙌

[fmvilas]

You have conflicts in the package-lock.json file. My suggestion is that you fix it by doing git pull (you'll get the conflicts in your machine), remove package-lock.json and node_modules, and then run npm install. After that, just continue the usual git commit workflow.

[derberg]

just my suggestion is that better do not remove package-lock.json as the installation that will follow will pump all the available patches of all dependencies. I once in the past got nice tip that it is enough to resolve conflicts in package.json and then run npm i --verbose and package-lock.json will be properly fixed

[Souvikns]

getting this error in tests

(node:51125) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 21 error listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
    (Use `node --trace-warnings ...` to show where the warning was created)

I see that the MaxListeners were increased,

cli/test/jest.setup.ts

Line 14 in 6e1484b

require('events').EventEmitter.defaultMaxListeners = 20;

I am unable to understand why this has to be increased and does this affect this error.

@derberg, @magicmatatjahu

[peter-rr]

I just ran the command locally and it works like a charm, one thing though I see it is not generating any spec file, when I do npm run dev it gives me this error.

I think we can solve this by generating a spec file to go with the functions.

This should be working fine after updating the .gitignore file. Could you check it?

[derberg]

@peter-rr @Souvikns this PR resolves #184 imho, and if we want similar stuff for Generator templates, IMHO would be better if @peter-rr opens a new issue really

wdyt?

[derberg]

@peter-rr @Souvikns sorry, actually #337 is there already, so @peter-rr imho just update PR description that #184 will be resolved with merge of this PR

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[peter-rr]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 0.39.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀