Use standard_types in templates (allow ipaddress, dns, uri, email in template).#1993
Use standard_types in templates (allow ipaddress, dns, uri, email in template).#1993geeknoid merged 3 commits intoistio:masterfrom
Conversation
|
@guptasu: Adding do-not-merge/release-note-label-needed because the release note process has not been followed. DetailsOne of the following labels is required "release-note", "release-note-action-required", or "release-note-none". Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Codecov Report
@@ Coverage Diff @@
## master #1993 +/- ##
==========================================
- Coverage 79.78% 79.51% -0.27%
==========================================
Files 71 66 -5
Lines 6758 6303 -455
==========================================
- Hits 5392 5012 -380
+ Misses 1089 1045 -44
+ Partials 277 246 -31
Continue to review full report at Codecov.
|
geeknoid
left a comment
There was a problem hiding this comment.
We probably should update the template dev guide along with this PR.
mixer/pkg/adapter/standardTypes.go
Outdated
There was a problem hiding this comment.
As discussed offline, we should do this but it needs work on the evaluator. For now I have marked the corresponding types inside mixer/v1/template/standard_types.proto as DO NOT USE. I will leave the rest of the code as is so that we have the tests and everything ready to be used once the evaluator code is ready.
There was a problem hiding this comment.
As discussed offline, we should do this but it needs work on the evaluator. For now I have marked the corresponding types inside mixer/v1/template/standard_types.proto as DO NOT USE. I will leave the rest of the code as is so that we have the tests and everything ready to be used once the evaluator code is ready.
mixer/pkg/adapter/standardTypes.go
Outdated
There was a problem hiding this comment.
As discussed offline, we should do this but it needs work on the evaluator. For now I have marked the corresponding types inside mixer/v1/template/standard_types.proto as DO NOT USE. I will leave the rest of the code as is so that we have the tests and everything ready to be used once the evaluator code is ready.
There was a problem hiding this comment.
As discussed offline, we should do this but it needs work on the evaluator. For now I have marked the corresponding types inside mixer/v1/template/standard_types.proto as DO NOT USE. I will leave the rest of the code as is so that we have the tests and everything ready to be used once the evaluator code is ready.
There was a problem hiding this comment.
Should make this a valid address so validations will succeed here (if we use actual type mail.Address
There was a problem hiding this comment.
Will leave this as is since we are not using the mail.Address. And as soon as we use mail.Address, this test should fail.
There was a problem hiding this comment.
Similarly, this should be a valid URL.
There was a problem hiding this comment.
Will leave this as is since we are not using the url.URL. And as soon as we use url.URL, this test should fail.
mixer/pkg/adapter/standardTypes.go
Outdated
There was a problem hiding this comment.
As discussed offline, we should do this but it needs work on the evaluator. For now I have marked the corresponding types inside mixer/v1/template/standard_types.proto as DO NOT USE. I will leave the rest of the code as is so that we have the tests and everything ready to be used once the evaluator code is ready.
mixer/pkg/adapter/standardTypes.go
Outdated
There was a problem hiding this comment.
As discussed offline, we should do this but it needs work on the evaluator. For now I have marked the corresponding types inside mixer/v1/template/standard_types.proto as DO NOT USE. I will leave the rest of the code as is so that we have the tests and everything ready to be used once the evaluator code is ready.
There was a problem hiding this comment.
Will leave this as is since we are not using the mail.Address. And as soon as we use mail.Address, this test should fail.
There was a problem hiding this comment.
Will leave this as is since we are not using the url.URL. And as soon as we use url.URL, this test should fail.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: geeknoid The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
What this PR does / why we need it:
This PR contains following changes.
Other Changes
[]bytefor IP_ADDRESSWhich issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release note: