Open EraKin575 opened 5 months ago
Welcome @EraKin575! It looks like this is your first PR to knative/client 🎉
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: EraKin575 Once this PR has been reviewed and has the lgtm label, please assign vyasgun for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Hi @EraKin575. Thanks for your PR.
I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/ok-to-test
Attention: Patch coverage is 50.00000%
with 2 lines
in your changes missing coverage. Please review.
Project coverage is 76.81%. Comparing base (
543b2b8
) to head (5e1ce9f
). Report is 12 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
pkg/kn/flags/channel_types.go | 50.00% | 1 Missing and 1 partial :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@EraKin575 thanks for the contribution and looking into the issue.
My idea from #1871 to align --channel
flag with the existing parsing logic from sink. Please feel free to evaluate the code and let me know if it's possible or not. Priority is to make UX feel the same, for --sink or --channel.
https://github.com/knative/client/blob/main/pkg/kn/commands/flags/sink.go
@EraKin575 thanks for the contribution and looking into the issue.
My idea from #1871 to align
--channel
flag with the existing parsing logic from sink. Please feel free to evaluate the code and let me know if it's possible or not. Priority is to make UX feel the same, for --sink or --channel.https://github.com/knative/client/blob/main/pkg/kn/commands/flags/sink.go
make it a common function for both sink and channel flags, right?
@EraKin575 thanks for the contribution and looking into the issue. My idea from #1871 to align
--channel
flag with the existing parsing logic from sink. Please feel free to evaluate the code and let me know if it's possible or not. Priority is to make UX feel the same, for --sink or --channel. https://github.com/knative/client/blob/main/pkg/kn/commands/flags/sink.gomake it a common function for both sink and channel flags, right?
Yes, exactly that.
PR needs rebase.
Description
Refactor the ChannelRef structure's Parse method to utilize the common implementation for parsing GVK formats.
Changes
modified channel flag parsing to align with sink flag *
Reference
Fixes #1871
Release Note