These are chat archives for ramda/ramda

9th
Feb 2015
Nate Wildermuth
@wildermuthn
Feb 09 2015 03:44
What's the workflow for getting an update to github pages?
David Chambers
@davidchambers
Feb 09 2015 03:59
Until this point I believe we've been pulling master into gh-pages with each release. That's not ideal for fixing typos and other errors, though.
As of right now, though, point your pull requests at master.
Nate Wildermuth
@wildermuthn
Feb 09 2015 16:17
Could documentation changes be put in a different branch so that they could be released quicker? I feel like incorrect or broken documentation impedes adoption. I know that I haven't been able to find functions lately. The search function is great, but only useful to people who already know the function they are looking for. For a beginner like myself, I don't know what I'm looking for by name. So it's really important to be able to filter by type.
If there was a documentation branch, then that could be targeted for all pull requests related to documentation, and be built without creating another Ramda release.
Scott Sauyet
@CrossEye
Feb 09 2015 16:27
It's funny, we've recently moved them back from an entirely separate project into the main project, but I agree that the change process for the docs is not right. We definitely need to do something. One goal is to keep several sets, one for each released version and one for the current HEAD. But doc fixes need to be easy to do. I am unable to build the docs right now, so I can't seem to help at all. I haven't figured out why. But I've tried on two different versions of Windows and one of Ubuntu. It just seems to be me.
dodo
@lazybean
Feb 09 2015 17:35

Hi there! The cloudfare url from the doc seems broken: or from a CDN, either cdnjs:

<script src="//cdnjs.cloudflare.com/ajax/libs/ramda/0.9.1/ramda.min.js"></script>

the jsdeliver is working fine though.
Jethro Larson
@jethrolarson
Feb 09 2015 18:44
It'd be nice if the unminified version was on jsdeliver as well. I'll often include ramda in jsbin experiments and debugging stuff on the minified version is harder.
David Chambers
@davidchambers
Feb 09 2015 18:50
I'm not sure of jsDelivr's policy. If they accept unminified files I'm fine with including that as well.
Scott Sauyet
@CrossEye
Feb 09 2015 18:55
I know that when we set it up at least one these the CDNs did not allow the non-minified file. I can't remember which one. I agree with @jethrolarson that I would really like to have it available, and parallel to the minified version.
Scott Sauyet
@CrossEye
Feb 09 2015 18:59
Yes, they have usually picked up the publishes to NPM. I don't know why that's broken, and they're stuck at 0.8.0. I'll look into it.
dodo
@lazybean
Feb 09 2015 19:00
Ok! thanks a lot
David Chambers
@davidchambers
Feb 09 2015 19:01
Probably because we moved ramda.js in 0.9.0.
Scott Sauyet
@CrossEye
Feb 09 2015 19:01
I don't remember now how we told cdnjs where ramda is. It was probably a fork and describe our library scenario, right?
Yes, the package.json in the ramda folder for the cdnjs repo includes this:
"npmFileMap": [
{
"files": [
"ramda.js",
"ramda.min.js"
]
}
],
David Chambers
@davidchambers
Feb 09 2015 19:04
Presumably if we prepend dist/ we should be okay.
Scott Sauyet
@CrossEye
Feb 09 2015 19:06
That's what I'm guessing. I'll try it. I just don't know if it will pick up the old versions. I'll try to publish with 0.9.1, and see if it finds the old one too. I'll check for some documentation first.
Scott Sauyet
@CrossEye
Feb 09 2015 19:42
This message was deleted
I also just noticed that we're pushing a great deal more than necessary in our NPM pushes.
David Chambers
@davidchambers
Feb 09 2015 21:34
The src directory, do you mean?
We should switch to listing in package.json the files we do want to include.
Scott Sauyet
@CrossEye
Feb 09 2015 22:15
A fresh install got me the folders dist, ext, jsdoc-template, less, src, and tasks and the files .gitattributes, CONTRIBUTING.md, LICENSE.txt, package.json, README.md and template.js. To my mind it should include dist, ext, LICENSE.txt, package.json, README.md, and quite possibly src. I don't think any of the rest belongs. Even ext should be going away if we're moving in the direction of separate repositories for the extensions.