These are chat archives for ramda/ramda

2nd
Dec 2014
David Chambers
@davidchambers
Dec 02 2014 03:03
Once we merge ramda/ramda#618, do we want to update ramda.js with each commit or with each release? For certain use cases (e.g. jsPerf) having the latest code available at all times in a single file is great. I'm in favour of updating the file with each commit. If others are of the same mind I'll update the PR so that npm test && make lint will fail if ramda.js is out of date.
Michael Hurley
@buzzdecafe
Dec 02 2014 15:23
each commit sounds good. should we move it to a dist/ dir, and should we move parts to a src/ dir instead of lib/?
David Chambers
@davidchambers
Dec 02 2014 16:36
Moving ramda.js to dist/ramda.js might be a good idea. If we do not, I imagine we'll get pull requests which update the generated file rather than the appropriate source file. As for src versus lib, I don't have a strong leaning in either direction.
Michael Hurley
@buzzdecafe
Dec 02 2014 17:32
i'd like to move sauce and bench/ under lib/ since they are not really top-level concerns IMO
but i don't like having all the source files in there too, would rather see a src/ dir
David Chambers
@davidchambers
Dec 02 2014 17:51
Okay. I'll update the PR.