I guess in theory you could enter the array indicies in as a string but that seems pretty hideous as a workaround and isn't the type of general purpose thing that tons of people would like
@RestartMV The initial version of Underscore took inspiration from a couple of other libraries, one of which actually did use string shorthands for all kinds of things. I guess that besides ugliness, it's also rather inefficient because of the additional parsing required, but it's still interesting. https://web.archive.org/web/20081201075555/https://osteele.com/sources/javascript/functional/
Hey All! Just wanted to pop by and say it seems cnn.com/activate isn't loading properly, and I see it's trying to fetch
https://underscorejs.org/underscore-min.js and getting a 404. Not sure if that's something controlled by these maintainers
Seems there's another request failing on that page, so it might not just be that. Anyway, night all!
Just https://www.cnn.com/feedback - but ironically that seems broken too lol. Though after hitting Submit it does look like a POST request is made. I reached out to them citing your tweet
@dylanlive I just released 1.13.1, which puts back the
underscore.js alias in git and on the website. That means that cnn.com/activate is un-broken for now, though I find it worrying that they haven't already switched to a CDN url.
Underscore was JavaScript Library of the Year 2021 according to w3techs.com! https://w3techs.com/blog/entry/web_technologies_of_the_year_2021 (third category on the page)
as i can see _.result() does not support invoke arguments and it makes it useless with arrow functions.
const obj = {
propertyA: 'foo',
propertyB: obj => obj.propertyA,
propertyC() { return this.propertyA; }
}
_.result(obj,'propertyB'); // will throw
_.result(obj,'propertyC');so, i am interesting how you solve that in your projects? do you just do not use arrow functions or you implement some other _.result able to handle this ?
_.powerResult(obj, property, [invokeArgs], defaultValue):
_.powerResult(obj, property, defaultValue) = obj.property.call(obj, obj)
_.powerResult(obj, property, nonArrayInvokeArgument, defaultValue) = obj.property.call(obj, nonArrayInvokeArgument)
_.powerResult(obj, property, [arg1, arg2], defaultValue) = obj.property.apply(obj, [arg1, arg2])when calling result with 2 or 3 params - behave mostly as usual except passing obj as first argument
when calling result with 4 params - take third param as invoke argument/arguments.
But i don't use _.result in my applications because i dislike that idea of invoking property of object and because of current limitation.
It seems that this method was invented for some certain case.
Personally i prefer to have invokeValue
function invokeValue(value, invokeArgs, invokeContext) {
...
}
and after some thoughts
in additional to described powerResult signatures
the main one should look like
and options can be something like this
in additional to described powerResult signatures
the main one should look like
_.powerResult(obj, property, options)and options can be something like this
{
defaultValue: any, optional,
invokeArgs: any, optional // array or single value shoud be handled separated
invokeContext: any, optional
}
but there could be some cavetas between
powerResult(obj, property, defaultValue) && powerResult(obj, property, options) :(
maybe this could do the job:
but as i told you before i am not using result at the moment because of its design.
powerResult(obj, options, property)but as i told you before i am not using result at the moment because of its design.
The usecase that
_.result was conceived for, I think, is in OOP situations where a value may be obtained from an instance either through a fixed property value or a zero-argument method. It is used a lot under the hood of Backbone, for example for Model#urlRoot/Model#urlRoot(). I do personally use it occasionally for this purpose, even outside of Backbone.
I have sometimes wondered whether the existing
_.result should support passing arguments. It could be extended to accept a fourth argument.
but backbone is a backbone. i just point to some strange things (in my opinion)
In any case, there weren't that many of such occasions.
actually i have some personal pack, so its not really copy paste
but... it seems to me pretty common in most cases.
but... it seems to me pretty common in most cases.
invokeValue(String) in my ideal world should not invoke
and i have a solution for that case
i put there all constructors
just retun it as is
this is for case when you may or may not set as property some of constructor and that property by design could be a function
view.extend({
childView: MyOtherView, // ok
childView() { // this is OK too
if (condition1) {
return View1;
} else {
return View2;
}
}
})
few days ago i've put that in a lib
https://github.com/taburetkin/yaff-entitybuilder
some util pack which i use in marionette
but actually it can be used in any framework
https://github.com/taburetkin/yaff-entitybuilder
some util pack which i use in marionette
but actually it can be used in any framework