Unset lost-column?

[iest]

From what I can see there's no way just to undo any lost-columns that are added. Are there any plans to support this or shall I just stick to using lost-column: 1/1?

[corysimmons]

What does lost-column: auto do? I haven't used Lost in a while so I forget my own syntax. 💃

[corysimmons]

If lost-column: 1/1 works for you then I'd just continue using that.

[iest]

I've ran into this again...

Had to resort to pretty horrid unsetting like so:

.links li {
  lost-column: 1/2 5 0;
}
.links .spacer,
.links .cta {
  lost-column: 1/1 1 0;
}

/* Then later... */
.links .spacer:nth-child(1n),
.links .spacer:nth-child(1n + 1),
.links .spacer:nth-child(n),
.links .cta:nth-child(1n),
.links .cta:nth-child(1n + 1),
.links .cta:last-child,
.links li:nth-child(n) {
  float: inherit;
  clear: inherit;
  margin-right: inherit;
  width: inherit;
}

@corysimmons where should I get started if I wanted to implement lost-column: auto?

[sarith]

I'd rather see this implemented as lost-column: none or something. We definitely need the ability to completely clear lost's added rules (for example, on different breakpoints to overwrite them).

[corysimmons]

Reopening. There should be a way to reset lost-column.

[peterramsing]

I'm with @sarith. A team I work with has been having to overwrite at different breakpoints as well. I've been playing with adding a lost-column: none rule and time permitting I'll see if I can wrap something into a pull request in the future.

[corysimmons]

@peterramsing Would really appreciate that PR. :)

[peterramsing]

@corysimmons I'm playing with a conditional at the top of the lib/lost-column.js file that looks for `none.

Working copy of file Gist

foo {
  lost-column: none;
}

The outputted CSS is:

foo {
  width: inherit;
}
foo:last-child {
  float: inherit;
  clear: inherit;
  margin-right: inherit;
  width: inherit;
}
foo:nth-child(n) {
  float: inherit;
  clear: inherit;
  margin-right: inherit;
  width: inherit;
}
foo:nth-child(1n + 1) {
  float: inherit;
  clear: inherit;
  margin-right: inherit;
  width: inherit;
}
foo:nth-child(1n) {
  float: inherit;
  clear: inherit;
  margin-right: inherit;
  width: inherit;
}

I want to make it a bit more intelligent than that I think, but maybe it could be that simple. It was a quick hack I threw in on a flight so I'm still testing it but wanted your thoughts on if it could indeed be that simple since you know the codebase a lot better than I (I'm just diving into PostCSS, too).

Regarding Sytax

Also, I don't want to just assume the syntax should be "none" to clear. Maybe this is a lost-utility instead of a part of lost-column. What do you think for direction? Maybe unset might be a better option?

[peterramsing]

@corysimmons We're running into this again in our codebase again and I'd love do see if we could implement this feature. Have any feedback?

[peterramsing]

Tested this more and the current version is working well but @corysimmons –let me know if this feels too hacky. I'll get a PR going so we can discuss this more there.

[corysimmons]

How about lost-column: reset? I'm also happy with none.