Add and fix test cases for emptyLineBeforeUnspecified

[hudochenkov]

Related to #87

[njbraun]

Are you suggesting this should pass with emptyLineBeforeUnspecified: 'always', set? I was under the impression this should fail. Anything that isn't a 'height' or 'width' css property should classify as "unspecified" and therefore should have an empty line before it w/ the above config.

That being said, if something isn't a standard css property (e.g. a comment, or the start of a new css selector block), that creates kind of a natural separation.

Let me know what you are thinking.

[hudochenkov]

We ignore requirement if there is a comment before. Take a look at these tests for emptyLineBefore:

stylelint-order/rules/properties-order/tests/empty-line-before.js

Lines 90 to 99 in b003219

	{
	description: '7',
	code: `
	a {
	display: none;
	/* comment */
	position: absolute;
	}
	`,
	},

stylelint-order/rules/properties-order/tests/empty-line-before.js

Lines 111 to 122 in b003219

	{
	description: '9',
	code: `
	a {
	/* comment */
	display: none;
	/* comment */
	position: absolute;
	}
	`,
	},

They are both accepted when emptyLineBefore: "always" is set for position.

[hudochenkov]

Word “unspecified” in properties-order rule always mean properties which are not specified in a config.

[njbraun]

Thanks for clarifying, I should have a PR up soon for this then.