example for feature #89

[jogibear9988]

Types of Changes

Prerequisites

Please make sure you can check the following two boxes:

• I have read the CONTRIBUTING document
• My code follows the code style of this project

Contribution Type

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue, please reference the issue id)
• New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
• Breaking change (fix or feature that would cause existing functionality to change)
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

Description

example for feature of minification of css #89

[FlorianRappl]

These are public. Can you keep them static readonly?

[jogibear9988]

I changed them to "const" so I could use them in a switch. But this could be reverted. Maybe it also works with new patern matching switch without that change.

What do you think about the overall concept? Is this a way to do Simplification/Minification of CSS as part of AngleSharp.Css ?

[FlorianRappl]

What do you think about the overall concept? Is this a way to do Simplification/Minification of CSS as part of AngleSharp.Css ?

Yeah we can leave it like that - personally I think for consistency having a dedicated formatter would make sense, too, but this also works.

I changed them to "const" so I could use them in a switch. But this could be reverted. Maybe it also works with new patern matching switch without that change.

Understood - yes, I think it does work in the pattern matching style using references.

[FlorianRappl]

Will be part of 1.0.0