Feature request

[deviprsd]

min and max functions are available but not documented, do document.

[seven-phases-max]

see https://github.com/less/less-docs

[deviprsd]

I mean the official website lesscss.org. Mention it there.

[jonschlinkert]

The new docs are for the official less website.

[deviprsd]

ok ... when are they coming up

[lukeapage]

On the changes section of lesscss.org it links to the site. Once I have the
usage section more fleshed out maybe the next step is a bigger notice on
the front page?

[deviprsd]

Cool ... 🎱

[seven-phases-max]

Offtopic. That's the fan part - I still can't understand why Bootstrap guys so pertinaciously ignore the documentation of the language they use. OK, the less-docs is in WIP and it may be not so easy to find something yet but at least they could read the changelog! :) I'm talking not only about those minmax functions but also about many many other features, e.g:

@cvrebert: Given the significant limitations of LESS, I don't believe this is realistically possible. It'd probably be doable in the **** port though (since it actually supports lists!).

Doh!

[jonschlinkert]

@seven-phases-max keep in mind that half the maintainers of less.js don't even know the latest all the time - @lukeapage (and now you) are just making so much progress that it's hard for anyone to keep! and the Bootstrap guys look to us for help and guidance. They have played a huge role in making less.js as popular as it is, we should be more proactive in helping them stay up to date.

[SomMeri]

@seven-phases-max I learned about changelog only few days ago :). Following and understanding all discussions in this repo requires a lot of time (imho) and a lot of that time is spend reading about things that are going to be discarded later on. So I understand that people working on other things do not know better.

This is where blog or tweet feed could help a lot. News about changes could come to people without them having to dig through every comment in repo. Maybe we could promote changelog more, it is an awesome thing :)

[jonschlinkert]

Maybe we could promote changelog more, it is an awesome thing :)

Agreed! @lukeapage does a great job of keeping it up to date!

[deviprsd]

Redemption

[cvrebert]

@seven-phases-max Protip: Folks trying to figure out if a feature exists generally consult hosted reference docs (e.g. http://lesscss.org), not a changelog or a docs git repo. Sorry my comment wasn't accurate, but missing/outdated docs certainly didn't help the situation.

If there's new stuff that can make https://github.com/twbs/bootstrap/blob/1736bcb05cb2c0b96825099fbb05b93ba4f327e5/less/mixins.less#L749 less horrible (no pun intended), I am all ears.

[seven-phases-max]

@cerbert,

mixins.less#L749

I'm afraid that this mixin is not the best example of "a list use-case" since the way it is now we don't need any "list" there: bs749.less (just an example, I don't actually think that for the moment it makes sense to change it in the BS). Upd: see also twbs/bootstrap#14410.

(My apologies if my comment above appears to be offensive or a sort of, of course I did not mean it to be that way)
But to answer the original sentence that triggered my amazement ("since it actually supports lists!"), here's a couple of LESS list/array usage examples (assuming that the repo where you can find the documentation for the corresponding functions is now evident):

• http://stackoverflow.com/a/21011089/2712740
• Handling scalar values with extract and length functions. #1576
• http://stackoverflow.com/a/20608729/2712740
• http://stackoverflow.com/a/20072967/2712740
• http://stackoverflow.com/a/19746260/2712740
• http://stackoverflow.com/a/20200431/2712740

I guess these examples give a basic idea of lists in LESS. So in context of #12039 there's nothing impossible.
Strictly speaking there's one missing function in the LESS "List Support" category: for the moment it is impossible to concatenate one list (or a single value) to another list. Simple junction via variable creates a two-dimensional list and a concatenation via ~"" creates a scalar value, so some function like concat or join would be handy. But here we enter the usual no-usecases->no-support->no-usecases dependency, i.e. nobody uses LESS lists -> nobody bothers to consider improving them (I would already proposed and implemented concat, but for the moment it would look just like Max is pushing features for his personal private use so I don't even bother :)

---

Protip: Folks trying to figure out if a feature exists generally consult hosted reference docs

Sure, and as you can see now we're doing our best to get less/less-docs ready soon, but I still think it is relatively rational for someone involved a little deeper than just "folks" to go a little beyond "Not in getbootstrap.com == Not in Bootstrap", how do you think? (yet again, no pun intended, after all I can always use "I'm not a native speaker" excuses :)

[cvrebert]

bs749.less

😍 That's pretty awesome. If only we could &:extend a 0-parameter mixin and thus avoid the dummy class...? 🙇

for someone involved a little deeper than just "folks" to go a little beyond "Not in getbootstrap.com == Not in Bootstrap", how do you think?

I would agree, however, I don't count myself as a developer of LESS, just a user of LESS (& admittedly of only intermediate LESS skill).
When Bootstrap users file issues about stuff that's addressed in the bleeding-edge version of the docs that has yet to be deployed to getbootstrap.com, I am still annoyed, but I don't fault the user. However, if the person was making a pull request, then I would justifiably be more perturbed.

Strictly speaking there's one missing function in the LESS "List Support" category: for the moment it is impossible to concatenate one list (or a single value) to another list.
[...] some function like concat or join would be handy.

Yeah, from my admittedly limited perspective, that seems pretty essential.

[seven-phases-max]

If only we could &:extend a 0-parameter mixin and thus avoid the dummy class...?

Yes, this is discussed in #1177, but so far I guess everybody are just waiting for @lukeapage to implement it (well, extend support is pretty much complicated already so it's just fearful to touch anything there w/o breaking something :).

[donaldpipowitch]

On the changes section of lesscss.org it links to the site. Once I have the
usage section more fleshed out maybe the next step is a bigger notice on
the front page?

I think this should had happen as soon as work on less/less-docs started. I've had problems because I didn't know about it, too.

The new docs are for the official less website.

Yep, this should be on lesscss.org with big lessons! Oh, and please kill translations if they are old and nobody updates them. I was redirected a lot to lesscss.de before knowing about an english version. Guess what: The german translation is for version 1.3.3!

at least they could read the changelog

Changelogs aren't my preferred way to read updates in frameworks and I tell you why: as far as I know I can't get the RSS feed to updates on a single file in a GitHub repo. (And even if I could I would only need the delta and not the whole changelog in my RSS reader.) That's a major bummer for me and if anyone of you know someone at GitHub, please tell them about this problem. (I think I've tried to tweet GitHub service about this before, but didn't got a useful response...)
I guess this is a problem for other people, too, as they try to get 3rd-party services for this which should be a general GitHub feature (e.g. nwjs/nw.js#297).

[matthew-dean]

Just for $0.02 - Agree that if the information is on Github, it does not mean the general user base of Less is informed. Yes, lesscss.org should have a notice that information is currently getting updated and may not be current. Translations should be dropped if we don't have the resources to keep them up to date.

[seven-phases-max]

(Inspired by #1826) Just in case, there's an optimized version (with "no dummy classes") of bs749.less mentioned above. There's no reason to use escaped strings for column classes generation. (I.e. #1177 will make it better but it is not the showstopper).