-
Notifications
You must be signed in to change notification settings - Fork 107
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
Ensure Consistent Use of MeshKit Errors in Meshery-Istio. #679
Comments
Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Contributors' Welcome Guide and sure to join the community Slack. |
I would like to work on this issue but may need some help |
Hey @thedeeppp, don't forget to post your question in the discussion forum or in Slack. |
@singh1203 , is the above task done or can you please provide some direct helping resources so that I can give it a try? |
@ShivanshuGupta07 @thedeeppp Thanks for waiting. Here's the Meshery Docs for running the adapter in your local development environment. Let me know if you need further guidance. |
|
Sorry, by mistake I unassigned myself, @singh1203 can you please reassign me |
Current Behavior
Currently, there are instances where errors are being used directly instead of MeshKit errors, which impacts the consistency and quality of error reporting across the project.
Desired Behavior
References
Meshery Documentation on Meshkit
Make sure to follow these guidelines during writing Meshkit errors
https://discuss.layer5.io/t/best-practices-for-writing-meshkit-errors/5536
Also here is an example PR to which you can refer:
#11340
Contributor Guides and Resources
The text was updated successfully, but these errors were encountered: