Skip to content
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

feat: add modelName to warning log #1997

Merged
merged 2 commits into from
May 13, 2024

Conversation

gitankit7
Copy link
Contributor

@gitankit7 gitankit7 commented May 11, 2024

refactor: Adding modelName to the warning log.

Description

refactor: Added modelName to the warning log to explicitly mention the model in the logs which is running into a warning state while generating models

Checklist

  • [ ✅ ] The code follows the project's coding standards and is properly linted (npm run lint).
  • [ ✅ ] Tests have been added or updated to cover the changes.
  • [ ✅ ] Documentation has been updated to reflect the changes.
  • [ ✅ ] All tests pass successfully locally.(npm run test).

Copy link
Contributor

@github-actions github-actions bot left a 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.

Copy link

netlify bot commented May 11, 2024

Deploy Preview for modelina canceled.

Name Link
🔨 Latest commit 6729605
🔍 Latest deploy log https://app.netlify.com/sites/modelina/deploys/6640f4ad0a5c5f0008408155

@gitankit7 gitankit7 changed the title Adding modelName to warning log to know which model conversion is run… refactor: Adding modelName to warning log to know which model conversion is run… May 11, 2024
@gitankit7 gitankit7 changed the title refactor: Adding modelName to warning log to know which model conversion is run… refactor: adding modelName to warning log to know which model conversion is run… May 11, 2024
@jonaslagoni jonaslagoni changed the title refactor: adding modelName to warning log to know which model conversion is run… feat: add modelName to warning log May 12, 2024
jonaslagoni
jonaslagoni previously approved these changes May 12, 2024
Copy link
Member

@jonaslagoni jonaslagoni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤙

@jonaslagoni
Copy link
Member

/rtm

@coveralls
Copy link

coveralls commented May 12, 2024

Pull Request Test Coverage Report for Build 9052894241

Details

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 92.3%

Totals Coverage Status
Change from base Build 9026084778: 0.0%
Covered Lines: 5995
Relevant Lines: 6326

💛 - Coveralls

@jonaslagoni
Copy link
Member

@gitankit7 got a lint error ✌️

Copy link

sonarcloud bot commented May 12, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@gitankit7
Copy link
Contributor Author

@gitankit7 got a lint error ✌️

@jonaslagoni - Linter should be happy now. :)

@jonaslagoni jonaslagoni merged commit a1e6366 into asyncapi:master May 13, 2024
16 checks passed
@jonaslagoni
Copy link
Member

@all-contributors please add @gitankit7 for code

Copy link
Contributor

@jonaslagoni

I've put up a pull request to add @gitankit7! 🎉

@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 3.5.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants