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

Remove apis.FieldError in favor go error interface #620

Closed
engedaam opened this issue Oct 20, 2023 · 5 comments
Closed

Remove apis.FieldError in favor go error interface #620

engedaam opened this issue Oct 20, 2023 · 5 comments
Assignees
Labels
good-first-issue Good for newcomers kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. operational-excellence

Comments

@engedaam
Copy link
Contributor

Description

What problem are you trying to solve?

How important is this feature to you?

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@engedaam engedaam added good-first-issue Good for newcomers operational-excellence kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Oct 20, 2023
@engedaam engedaam changed the title Remove apis. FieldError in favor go error interface Remove apis.FieldError in favor go error interface Oct 20, 2023
@Sanskarzz
Copy link

/assign

@Bharadwajshivam28
Copy link
Member

/assign

@Bharadwajshivam28
Copy link
Member

Hello @engedaam i want to work on this issue sir

@Bharadwajshivam28
Copy link
Member

What I understand is that our goal is to-

  1. Remove the knative.dev/pkg usage
  2. Replacing the usage of apis.FieldError with interface

@Sanskarzz Sanskarzz removed their assignment Feb 10, 2024
@jonathan-innis
Copy link
Member

I'm questioning how much we want to do this actually because, as this is developing, I'm thinking that we are most likely going to end up keeping the webhook with knative but we will just create a separate module for the webhook. With that in mind, I think that we can probably punt on this for now until we get more clarity into how that webhook separation is going to work.

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 kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. operational-excellence
Projects
None yet
Development

No branches or pull requests

4 participants