The title is of course, misleading. We know from Javascript that we can't use the .map() method on non-arrays so what I am talking about? Let's say...
For further actions, you may consider blocking this person and/or reporting abuse
Sorry to say this, but this "trick" is just a workaround for a poorly designed api. If you have to implement such kind of stuff, you should really reconsider reimplementing your api.
If an api endpoint should return a list, it has to return a list even if it only contains one element.
While such workarounds are possible in js, there is no trivial way in doing this in eg C#. And if the same api should get used for a .net project, the c# devs will get mad at you :-)
I agree. In an ideal world, this would be true. But I'm talking more about the situation in which we're consuming APIs, not designing them. So the trick is not meant for the API devs but for the consumers who might run into issues because of unpredictable API results.
"Why aren’t objects iterable over properties, by default? The reasoning is as follows. There are two levels at which you can iterate in JavaScript:
The program level: iterating over properties means examining the structure of the program.
The data level: iterating over a data structure means examining the data managed by the program.
Making iteration over properties the default would mean mixing those levels, which would have two disadvantages:
You can’t iterate over the properties of data structures.
Once you iterate over the properties of an object, turning that object into a data structure would break your code. If engines were to implement iterability via a method Object.prototypeSymbol.iterator then there would be an additional caveat: Objects created via Object.create(null) wouldn’t be iterable, because Object.prototype is not in their prototype chain." - exploringjs.com/es6/ch_iteration.h...
Remember you can, in most of the cases, simply do:
This way, you only need to avoid
undefinedornullvalues.Why use forEach() instead of map()? ForEach returns
undefinedso you can't display anything on the page when looping through the array.Remember that the typical functions in JavaScript functional programming nowadays, are:
forEach,filter,map,reduce(the last one is the more powerful of all).We also have others, like:
Object.assignandObject.defineProperty.I mentioned
forEachbecause it is the simplest, not because it fit in the example.Thank you.
Thank you for your input.
Wouldn't it be better to just wrap the code to be executed for each item in a method and then call the method directly if it is single item?
Say, something like
hm, i just don't get the advantage here. is it synonym to
this useful when your response is usually a list of objects and you're using a map to output it, but when your response is a single item it's not in an array, it's just a single object and using map throw an error.
True, but how do you know if the response from the server has one object inside or an array of objects? You'll need to use different rendering methods (use map or not) depending on what you get from the fetch - so you would still need to make a check somewhere.
i thought array in response is no go, because haacked.com/archive/2008/11/20/ana...