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

Ensure Consistent Use of MeshKit Errors in meshery-kuma #438

Closed
2 tasks
singh1203 opened this issue Aug 22, 2024 · 5 comments
Closed
2 tasks

Ensure Consistent Use of MeshKit Errors in meshery-kuma #438

singh1203 opened this issue Aug 22, 2024 · 5 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed issue/stale Issue has not had any activity for an extended period of time kind/enhancement New feature or request language/go Issues or pull requests that use Golang

Comments

@singh1203
Copy link

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

  • Replace all direct usages of errors with MeshKit errors.
  • Ensure that each MeshKit error includes:- Short Description, Long Description, Probable Cause & Suggested

References

Meshery Documentation on Meshkit


Contributor Guides and Resources

@singh1203 singh1203 added kind/enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers language/go Issues or pull requests that use Golang labels Aug 22, 2024
Copy link

welcome bot commented Aug 22, 2024

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Contributors' Welcome Guide, engage in the discussion forum, and be sure to join the community Slack.

@alinaefi
Copy link

/assign

@TraXIcoN
Copy link

Hi, @singh1203 can this be assigned to me? Would love to work on this.

Copy link

stale bot commented Oct 17, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label Oct 17, 2024
Copy link

stale bot commented Oct 30, 2024

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

@stale stale bot closed this as completed Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed issue/stale Issue has not had any activity for an extended period of time kind/enhancement New feature or request language/go Issues or pull requests that use Golang
Projects
None yet
Development

No branches or pull requests

3 participants