Option for max attributes length

[ManUtopiK]

Hi!

I added an option to define the max length of the component's attributes.
I added tests for that.
The default stays the same 80 chars.
In the nuxt config, add this option:

mdcOptions: {
  maxAttributesLength: 100
},

I named the option maxAttributesLength but in fact, it's the length of the line, which include the name of the component and the decoration:

`::component{key="value"}` //  = 24 chars

Maybe we could found a better name for this. Naming is hard.
I didn't set this option in the experimental feature because it's a very small change...

Also, during development, maybe I found a possible issue that already exists before this merge request.
When this length is exceeded (default: 80), the attributes are converted to yaml format.
That's the point. But the fmAttributes are not properly filled and remains empty. You can see it in the snapshot.
This is not the case when we directly provide the component yaml props.
But if the length is exceeded, we are now in yaml style, so I think the fmAttributes should have the props.
It needs review because I don't know if it's the normal behavior...

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[farnabaz]

Thanks for the PR.

About the fmAttributes, I believe it is fine to keep fmAttributes empty on parsing.
parsing markdown and creating are separate from each other. Imagine If the limit in parse time is 80 and the limit for Stringify is 100.