-
-
Notifications
You must be signed in to change notification settings - Fork 170
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
test: replicate incorrect bundling and missing assertions part of #1323 #1389
base: master
Are you sure you want to change the base?
test: replicate incorrect bundling and missing assertions part of #1323 #1389
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.
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.
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.
Thanks for raising this draft! I left some comments :)
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.
Left some comments 😄
I've pulled and synced the changes from However, the corrected tests are now showing 1 new issue coming probably from the bundler. The bundler, since However, when running the tests, for ASyncAPI components:
messages:
TestMessage:
payload:
type: string
x-origin: '#/components/messages/TestMessage' This happens for both Right now this is the only thing keeping it failing. @peter-rr @Amzani @Souvikns @Shurtu-gal any thoughts how you'd like to proceed? Options I can think of:
Thanks! |
@francocm I have traced the issue up to the |
…ope of this PR will ignore the extra component block
Thanks for the analysis. Worth adding that although this component is ignored, when I have updated my PR to consider this outcome as expected in the tests, since the scope of this PR is on the issue raised in #1323 and:
Probably anything else needs to be done in a separate place, and could be tracked in a new issue + linked to the APIDevTools/json-schema-ref-parser#349 you raised. @peter-rr I've updated the PR with feedback, tests should be passing, and it's no longer a draft. Kindly let me know your thoughts at this stage. Thanks 🙂 |
/update |
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.
Hey @francocm, great work! 😄
The changes you have applied look good to me. However, all the tests related to bundle
command are not passing since I'm getting this error when executing the command for any test case:
Error: Unable to bundle specification file of different major versions
I've updated your branch with the latest changes from master but can't make the tests pass. Could you please try to run the tests again after updating your branch to check the result?
Also we're getting this error on the CI workflow related to linter. You can fix it easily by running npm run lint:fix
Yeah, I agree with this 👍 |
/update |
Hi @peter-rr, Thanks for following up. I've run Running
Full log:
|
Hello, @francocm! 👋🏼
|
Just realised, if it helps I'm using Node 20:
|
Thanks @francocm for the tip 👍 I've tried with v20 but still getting the errors. Also now I'm getting many errors during the building process after updating CLI to the latest version 1.14.0. Even working on master branch. Let me investigate why I'm getting those results 🤔 and I'll get back to you. |
@peter-rr |
Thanks @aeworxet 😄 I just needed npm-installing to include the latest version of |
@francocm Now this PR needs to be reviewed by the codeowners before being merged. |
/ptal |
@Amzani @Souvikns @Shurtu-gal Please take a look at this PR. Thanks! 👋 |
/update |
/update |
Quality Gate passedIssues Measures |
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.
@francocm could you add the spec files in test/fixtures as can be seen for others.
This pull request has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation. There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
still relevant @francocm are you still working on this? |
Description
true
inbundle.test.ts
. Existing tests also failing.Related issue(s)
Replicates #1323