Lost fails to parse fractions when the numerator and denominator are separated by spaces around the fraction bar.

[Lucassifoni]

Bug report

What is the current behavior?
This code sample works fine

.Export {
  &__candidates {
    display: flex;
    flex-wrap: wrap;
    width: 100%;

    & > div {
      lost-column: 1/4;
    }
  }
}

Whereas this one fails to generate proper code.

.Export {
  &__candidates {
    display: flex;
    flex-wrap: wrap;
    width: 100%;

    & > div {
      lost-column: 1 / 4;
    }
  }
}

If it's a bug please provide the steps to reproduce it and maybe some code samples.
Add spaces around the fraction bar / in a lost-column declaration.

What is the desired behavior?
With the above code samples, output should be similar to :

.Export__candidates > div:nth-child(n) {
    margin-right: 8px;
    margin-left: 0;
}
.Export__candidates > div {
    flex-grow: 0;
    flex-shrink: 0;
    flex-basis: calc(99.9% * 1/4 - (8px - 8px * 1/4));
    max-width: calc(99.9% * 1/4 - (8px - 8px * 1/4));
    width: calc(99.9% * 1/4 - (8px - 8px * 1/4));
}

but is :

.Export__candidates > div:nth-child(n) {
    margin-right: 4;
    margin-left: 0;
}
.Export__candidates > div {
    flex-grow: 0;
    flex-shrink: 0;
    flex-basis: calc(99.9% * 1 - (4 - 4 * 1));
    max-width: calc(99.9% * 1 - (4 - 4 * 1));
    width: calc(99.9% * 1 - (4 - 4 * 1));
}

What's the motivation or use-case behind changing the behavior?
Correctness and general ease of use by suppressing syntax-related bugs.

What version of LostGrid, browser and browser version are affected by this issue? Did this happen in previous versions?
Lost 8.3.0, related to codegen, not browser interpretation.

Anything else?
I'd like to tackle this issue, since I enjoyed working on #418

[peterramsing]

@Lucassifoni, Oi. Looks like something worth fixing.

I'm in meetings all week away from home so my brain is a bit cloudy on Lost–I want to say that this issue has either been brought up or was address some other time? Not sure. If I recall the specifics or look back on it on the plane I will ping back here.

I'd love it if you wanted to fix it. calc() supports this and that feels like a good pattern to ensure that we're following so this is certainly something worth fixing.

I'll label this up and let me know if you do end up starting on it.

[peterramsing]

Merged and released. 👍