RA.lensIso and RA.lensTraverse which you might be interested in reading and maybe responding to.
undefined by leveraging Sanctuary's Maybe. At times, this has been a real pro with adoption internally, because I don't have to both sell lenses and monads at the same time. After speaking with him, I see why he is doing it too.
lensTraverse. I hit the limitations of R.over/view he is describing, that is why it consumes explicitly the UNIT function. I did not want to create separate RA.view/over just for this function. Let's see what we'll come up with.
@/all I've just released v2.7.0 containing 3 new utils. Great job everyone! If you have twitter and linkedin accounts please reshare this posts
https://twitter.com/vladimirgorej/status/989015824487931904
https://www.linkedin.com/feed/update/urn:li:activity:6394781213374189568/
hey, i'm a little confused about lensISO
import * as R from 'ramda';
import qs from 'qs';
const queryString = 'foo=bar&bar=baz';
const queryStrLens = R.lens(qs.parse, qs.stringify);
const view = R.view(queryStrLens, queryString);
const modified = R.over(queryStrLens, R.assoc('bob', true), queryString);
document.getElementById("app").innerHTML = `
${JSON.stringify(view, null, 2)}
${JSON.stringify(modified, null, 2)}
`;i'm doing a workshop at work about lenses and always assumed i could just use R.lens to make isomorphic lenses, and my testing seems to work, so what is lensISO for?
@SeeThruHead pls refer to this article: https://www.linkedin.com/pulse/functional-lenses-javascript-isos-vladim%C3%ADr-gorej/
It contains the justification why it exists. The important part that your code it missing is reverting the isomorphism. When you need to reverse your isomorphism you have to create additional lens for it. RA.lensIso already knows how to do that and will create it for you. Observe
const queryStrLens = RA.lensIso(qs.parse, qs.stringify);
const queryString = 'foo=bar&bar=baz';
const parsedQueryString = qs.parse(queryString);
const view = R.view(RA.lensIso.from(queryStrLens), parsedQueryString);RA.lensIso is basically a factory for creating isomorphic lenses. You're declaratively saying that this lens is going to be isomoprhism and you get the reversion mechanism for free if you do so. That's what we try to do in Ramda-Adjunct. Create a compositions for common problems with descriptive declarative names.
@Undistraction this partially describes my lens naming conventions: https://www.linkedin.com/pulse/composing-lenses-ramda-vladim%C3%ADr-gorej/
But if I do something similar like you do in your code fragment I'm too using get and set prefixes for derived functions
@/all milestone for next release of 2.10.0 - https://github.com/char0n/ramda-adjunct/milestone/13
Let's see what we can manage, we can operatively do some infra related issues, and we should start planning going through all the issues. I am already trying to find some block of consistent time to go through them. We can do it in async or sync mode (using this chat)
ramda. Something must be wrong
Hi guys !
Sorry for my absence lately, I recently joined the Team Station (http://getstation.com) and I had to learn typescript.
So, I did not have the time to commit on ramda-adjunct repo.
I just introduced ramda and ramda-adjunct to my team. (I'm very glad about that :D)
I would be more active on ramda-adjunct now.
What are the cons ?
@Undistraction @guillaumearm I'm still in the discussion with legal, but what I know is that copyright notice will look like this in our license file: Copyright (c) 2018 Oracle and/or its affiliates along with the one that is already there. And the oracle will claim ownership of the commits I make during my employment. Technically every contributor to the library so far has right to request that we add copyright notice with his name; the author of the commits is the IP holder of the code. They can come and request removal of their code from the library too... It's perfectly within their rights. We don't use CLAs.
The question is more about do we want to have Oracle owned code inside the library ? And an explicit copyright notice in our license file ? Some companies/people will think twice before using this library if they see this notice there.
Oracle is making their contributions available under the MIT licencse.So it clear that the license is under which Oracles contributions are made are free and available.
mergeProp correct? In the parameters section it lists p as a type of Array, but shouldn't it be a String?https://char0n.github.io/ramda-adjunct/2.33.0/RA.html#.mergeProp