ache-sling.73963.n3.nabble.com/JS-Use-API-usability-or-limitations-tp4069490p4069550.html
Sent from the Sling - Users mailing list archive at Nabble.com.
lways struck me as kind of wasteful.
From: lancedolan <lance.do...@gmail.com>
Sent: Wednesday, January 11, 2017 4:41 PM
To: users@sling.apache.org
Subject: RE: JS Use API usability or limitations
No architectural reason - purely speed of development
.
--
View this message in context:
http://apache-sling.73963.n3.nabble.com/JS-Use-API-usability-or-limitations-tp4069490p4069526.html
Sent from the Sling - Users mailing list archive at Nabble.com.
@sling.apache.org
Subject: RE: JS Use API usability or limitations
Thank you for your time everybody! For posterity:
First to clarify, my very specific question is how to iterate an iterable in
the model-building logic (what us old timers might call a "backing bean"). I do
already know that I c
/idiomatic knowledge to give the sort of development speed one
would expect with JS. I'm going to keep it as an option for very simple
components.
--
View this message in context:
http://apache-sling.73963.n3.nabble.com/JS-Use-API-usability-or-limitations-tp4069490p4069521.html
Sent from the S
Hi Lance!
The problem is not the JS Use API but the way the JS Iterator is used. One
should do:
for (var [key, res] in Iterator(children)) {
returnObj.content += res.name;
}
Also, Robert is right, you should strive to keep your business logic (use
objects) as light as possible do the
Hi,
On Tue, 2017-01-10 at 18:29 -0700, lancedolan wrote:
> All I want to do is print out a resource's children resources.
Using the HTL repl [1] I narrowed down the following way of listing
child resources:
template.html
-
${properties.jcr:title}
My siblings are:
with sling models and unit tests.
stefan
>-Original Message-
>From: lancedolan [mailto:lance.do...@gmail.com]
>Sent: Wednesday, January 11, 2017 2:30 AM
>To: users@sling.apache.org
>Subject: JS Use API usability or limitations
>
>I've got years of experience writi
at limitations exist here? I was
planning on doing the same things in JS that I've always done in Java, which
is usually a lot of read/write operations on the JCR.
--
View this message in context:
http://apache-sling.73963.n3.nabble.com/JS-Use-API-usability-or-limitations-tp4069490.html
Sent fr
