Task #48479
Work Package #48275: TypoScript consistency
make priorities in @position before/after consistent
| Status: | Resolved | Start date: | 2013-05-23 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Sebastian Kurfuerst | % Done: | 100% |
|
| Category: | - | Spent time: | - | |
| Target version: | 1.0 beta 1 |
Description
Generally, when we use priorities in TypoScript @position, it always means:
"the higher the priority, the more certain you are that the desired outcome
happens". F.e. if s.th. is positioned "start 10000" it means "very certain
that it is positioned at the start"; for "end 10000" conversely, it means
"very certain that it is positioned at the end". If we do not specify an
priority, that defaults to "position $somewhere in this area with low
priority", e.g. priority 0.
When sorting keys before and after each other using "before [otherkey]"
and "after [otherkey]" respectively, we express that an element should
be "somewhere before/after" an element. The higher the priority, the
more close it should be towards the element. Before this change, it
was exactly the other way around which was counterintuitive.
Associated revisions
[BUGFIX] make priorities in @position before/after consistent
Generally, when we use priorities in TypoScript @position, it always means:
"the higher the priority, the more certain you are that the desired outcome
happens". F.e. if s.th. is positioned "start 10000" it means "very certain
that it is positioned at the start"; for "end 10000" conversely, it means
"very certain that it is positioned at the end". If we do not specify an
priority, that defaults to "position $somewhere in this area with low
priority", e.g. priority 0.
When sorting keys before and after each other using "before [otherkey]"
and "after [otherkey]" respectively, we express that an element should
be "somewhere before/after" an element. The higher the priority, the
more close it should be towards the element. Before this change, it
was exactly the other way around which was counterintuitive.
I noticed that during the documentation writing, and adjusted the tests
and implementation accordingly.
Resolves: #48479
Change-Id: Ida4a4e025901f1ca7d35ffe0dc45df31edc7ad4e
History
#1 Updated by Gerrit Code Review about 2 years ago
Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20991
#2 Updated by Sebastian Kurfuerst about 2 years ago
- Status changed from Accepted to Under Review
#3 Updated by Gerrit Code Review about 2 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20991
#4 Updated by Sebastian Kurfuerst about 2 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100