-
Notifications
You must be signed in to change notification settings - Fork 13
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
Relax Stickiness Rules for Strains with Conditions #254
Comments
Looking at the existing tests in
is expected to have canonical form:
What do you think, @trieloff : should I rework the stickyness in the expected output(s) or assume string-based conditions are always sticky, which as mentioned would make all tests pass? |
I'd phrase the old policy as: "when in doubt, treat it as sticky". Because we couldn't understand string based conditions, they were always sticky. With the new condition expressions, we can be more precise, and treat a condition like |
So, I remove the |
Yes. |
# [6.0.0](v5.3.1...v6.0.0) (2020-02-28) ### Documentation * **changelog:** mark 5.3.1 as a breaking change ([b556e6e](b556e6e)), closes [#256](#256) [#253](#253) [#254](#254) ### BREAKING CHANGES * **changelog:** The 5.3.1 release introduces breaking changes for conditions handling. This commit formally acknowledges that.
Previously, we assumed a strain with a
url
was not sticky, but a strain with acondition
was. Now, that URLs have moved below conditions, every strain with a condition is sticky, even if it wasn't before.I suggest we relax the stickiness rules so that the condition will actually be evaluated for stickiness.
Based on the list of conditions here, I'd suggest:
sticky
referer
url_param
** conditionally sticky** (sticky when at least one component condition is sticky)
and
or
not
not sticky
The text was updated successfully, but these errors were encountered: