Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Rework handling of ingress.class annotation #767
Rework handling of ingress.class annotation #767
Changes from 50 commits
c24b8a2
8f1cd94
1c9ab54
b5d972d
2f431a3
64098fe
cad2b23
75cc4da
bc0a387
dd917ac
513e394
dcc319c
7c696a6
25e7730
cbb0b2a
742cd89
284880f
cc030d2
0b8c7d1
fd8eac4
baace98
960900a
9456797
c4265c8
4f7c5a3
9d70471
b00d7ed
5f621c3
6158c25
8474870
1ccd6eb
be804bf
109061d
e946eb8
a2997ab
d869324
daf05f5
02335b6
e361c0a
33e32ef
eca131e
b076e95
d9fbc20
b0bfaa3
fb3ab86
2d0d44b
d933951
03fefa7
1bac620
e737aad
8fc0042
3570563
1bac3a4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest rewriting this test to have the following values in the table:
This would mean directly putting
ClassHandling
in the table, as opposed toskipClasslessIngress
(which adds apparently unnecessary complexity and makes it easier to miss missing cases or mistakes)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is essentially what it has now--I've added comments to clarify what's what.
What we don't have is tests of the strategies independent of their user-facing controls: the latter are boolean flags, and the former are derived from them. Effectively we have integration tests here, and a poor delineation between integration and unit tests throughout the codebase, alongside the poor separation between components (the store/annotation distinction is messy in both the tests and implementation).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My point is that this logic is unnecessary:
it could be as simple as
The problem here is that we have replicated a part of the "system under test" (namely, the
if
as quoted above) in the test itself. This is not right because it adds a degree of freedom to the actual system under test. Therefore, IMO it's better to remove theif
and update the test data to use aClassMatching
, not abool
as input.