Closed (outdated)
Project:
Drupal.org customizations
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
16 Jun 2014 at 23:18 UTC
Updated:
25 Feb 2020 at 14:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
stefan.r commentedComment #2
stefan.r commentedAs this feels a bit convoluted there is also the option of fixing the tests themselves to expect a
version = 7.xx(for the D7 test) orversion = 8.xxstring (for the D8 test) instead of the hardcodedversion = 1.0Comment #3
sunUnlike YAML in D8, the .info format parser (derived from INI) in D7 always consumes the last value of a property, if the property is specified multiple times.
For example:
yields:
The only sensible fix here would be to change the test in core to not have an absolute expectation... but that would defeat the test's purpose.
Comment #4
stefan.r commented@sun what if we change the test & info file to use the VERSION constant instead of 1.0? Isn't that the same version that will be appended by the packaging script?
Also just a heads up about the parsing order, if for D8 the packaging script is still going to append the new version after the previously defined one, it is a change in behavior as versions aren't "overwritten" anymore. But it would also mean this issue ceases to exist for the D8 test :)
Comment #5
drummOverriding the core compatibility line was removed with #3075062: Remove core key overriding in .info.yml packaging