Make the Declaration Order recommendation optional

This recommendation was relaxed in the internal style guide a few months ago. The suggestion is still to continue using alphabetical order unless teams have access to the appropriate tooling which can support consistently automating and enforcing different sorting rules which may be more logical to read.
This commit is contained in:
Tony Ruscoe 2022-05-06 11:48:31 +01:00 committed by GitHub
parent cada798ffe
commit 1faa779a12
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -735,10 +735,12 @@ frequently.</p>
<h4 id="Declaration_Order" class="numbered">Declaration Order</h4> <h4 id="Declaration_Order" class="numbered">Declaration Order</h4>
<p>Alphabetize declarations.</p> <p>Alphabetize declarations (optional).</p>
<p>Put declarations in alphabetical order in order to <p>Sort declarations consistently within a project. In the absence of tooling to
achieve consistent code in a way that is easy to remember and maintain.</p> automate and enforce a consistent sort order, consider putting declarations in
alphabetical order in order to achieve consistent code in a way that is easy to
learn, remember, and manually maintain.</p>
<p>Ignore vendor-specific prefixes for sorting purposes. However, multiple <p>Ignore vendor-specific prefixes for sorting purposes. However, multiple
vendor-specific prefixes for a certain CSS property should be kept sorted (e.g. vendor-specific prefixes for a certain CSS property should be kept sorted (e.g.