-
Notifications
You must be signed in to change notification settings - Fork 107
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
Fix and test nothing is GET sticky globally #1671
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
6 times, most recently
from
October 5, 2021 21:26
3ff9f65
to
1597000
Compare
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
3 times, most recently
from
October 10, 2021 21:32
0e9bb07
to
633ff98
Compare
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
9 times, most recently
from
November 12, 2021 19:06
e87bf30
to
f762ac8
Compare
mvorisek
commented
Nov 12, 2021
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
from
November 17, 2021 09:43
04b3d4b
to
d6ed6c3
Compare
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
from
November 30, 2021 11:14
9323ed2
to
ee46e42
Compare
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
2 times, most recently
from
January 18, 2022 23:04
e0c5b23
to
fc77193
Compare
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
from
February 13, 2022 10:53
fc77193
to
0dfffa9
Compare
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
2 times, most recently
from
February 13, 2022 12:01
53b677a
to
ed2d55d
Compare
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
from
April 8, 2022 16:38
3a2caa2
to
0cf9781
Compare
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
3 times, most recently
from
April 8, 2022 17:34
4295161
to
8600f7e
Compare
mvorisek
force-pushed
the
ensure_no_global_sticky
branch
from
April 8, 2022 17:46
645d8ac
to
368a126
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No global GET sticky is important design goal of component based atk4/ui and we must fix it and assert it across all tests.
The presented test should reject usages like in #1650 (comment)
Also removing
tools/get-assets.php
as it is dangerous to cache resources as they might become out-of-sync and for some files, such dummy caching is not enought, as the resources might access another resources using relative paths.