Mat Simon

@madeleineostoja oh that's great. The plugin looks really interesting. I completely agree that adding more API surface needs to be done thoughtfully, but I think that adding some kind of...

> As an aside if we did implement this the new fluid scale should largely mirror the existing font scale, just tween values based on viewport Yes agreed. I think...

> Line heights are unitless so you wouldn't need those to be fluid to maintain a proportionate fluid scale That is true, but still line heights change depending on size...

Yes, but if you create fluid typesets, then the line heights would possibly be fluid as well, since it's pretty common to reduce the line height for bigger fonts in...

I've started incorporating this in my personal project. I initially thought that the naming convention was not to use dashes in the names of the individual values of the modules,...

Glad you like it! Yes I agree. After the short discussion with you, I read up on it and came to the same conclusion. It's not even possible to change...

To add to this, I think an advantage of using `--scale-fluid-[x]` and `--size-fluid-[x]` would be that they are more easily discoverable. I was also thinking, whether it would make sense...

I don't personally have any use for this right now but adding grey values like this for rapid prototyping seems quite useful to me. Of course you can define the...

@IvanMathy just wanted to let you know that the latest version (1.5.0) does not seem to have fixed this issue.

Additionally I'm running into the issue here, where I don't see a solution other than creating a typescript function: ```svelte {#each submission.files as file} {file.originalFilename.split('.').pop()} {/each} ``` This fails as...