feat: introduce monorepo with filters package included

[ayushnau]

Changes Added.

1. Turborepo Added.
2. Converted the generator repo to app, inside the turborepo.
3. Added the required scripts of the turborepo to the root package.json file.

Related issue(s)

Resolves #1044

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[derberg]

this PR is huge

can we introduce the change at least in 2 PRs? like first add generator-filters and then move generator to apps? cause now you just did moved all other files inside apps/generator but without checking if it makes sense, like for example all GitHub workflows

[ayushnau]

this PR is huge

can we introduce the change at least in 2 PRs? like first add generator-filters and then move generator to apps? cause now you just did moved all other files inside apps/generator but without checking if it makes sense, like for example all GitHub workflows

@derberg should i convert the generator into turborepo. on its own. first . which means adding generator to the apps directory before as that would make sense.

Also prs of merging the repos will be expected to be huge even though i add one at time in a single pr. cause i am also merging the commits.

[derberg]

@ayushnau yeah, I know they will be big, we just need to figure some approach maybe that can show that new files that are added are not modified or something like that, so review is smooth

but yeah, in this particular PR I know that if you split in 2 it will be big anyway, but seeing you moving GH actions workflows inside apps made me think we need to do one app at a time

[ayushnau]

@ayushnau yeah, I know they will be big, we just need to figure some approach maybe that can show that new files that are added are not modified or something like that, so review is smooth

but yeah, in this particular PR I know that if you split in 2 it will be big anyway, but seeing you moving GH actions workflows inside apps made me think we need to do one app at a time

1. I think we can check by default in git which are only moved files

2. Actually I did removed the .github file but somehow the .github file changes didnt get added in the git changes.
3. Now I have removed the filter repo. Now it is just the generator repo.

[derberg]

• apps/generator/.all-contributorsrc must stay in the root
• same sonar clound properties config - should be one for all apps
• same eslint and editor config files right?
• same files like codeowners or code of conduct, license, contri guide
• same readme banner
• also readme seems to be duplicated

[ayushnau]

• apps/generator/.all-contributorsrc must stay in the root

  • same sonar clound properties config - should be one for all apps

  • same eslint and editor config files right?

  • same files like codeowners or code of conduct, license, contri guide

  • same readme banner

  • also readme seems to be duplicated

1. Ok and what about .editorConfig file. that also needs to be in root.

[derberg]

.editorConfig - yes, also in root

[derberg]

please lemme know once you make changes and resolve conflicts

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[ayushnau]

Acutually i was not able to get the changes in my branch. so need to refork it.

[ayushnau]

This pr is moved to this #1186