Re: Need a solution to install content with the teleported test
Hi Peter,
Good to read you here!
On Fri, Dec 11, 2015 at 5:49 PM, Peter Hunsberger
wrote:
> ...It's not clear why you even need the resetParent concept. Why not just
> build the two sets of resources separately? Eg:
>
> p.resource("a/b");
> p.resource("c/d"); ...
The ResourceBuilder is stateful, to make it easy to create content
hierarchies, so I think you need a way to tell it to restart at the
top in some cases - or implement pop() to go back up the stack of
created resources, but that makes it less intuitive IMO.
But maybe you have better ideas on how to express this example tree in
a fluent API?
> ├── apps
> │ ├── myapp
> │ │ └── components
> │ │ └── resource
> │ │ ├── models.js
> │ │ └── text.html
> │ └── myapp.json
> └── content (title:"foo")
> ├── myapp
> │ └── resource
> └── myapp.json
The current code for creating a similar tree is in
ResourceBuilderImplTest.treeWithFiles() [1]
-Bertrand
[1]
https://svn.apache.org/repos/asf/sling/trunk/bundles/commons/resourcebuilder/src/test/java/org/apache/sling/resourcebuilder/impl/ResourceBuilderImplTest.java
Re: Need a solution to install content with the teleported test
Ugh, I see. I had assumed a more functional style with the state travelling
with the return value, that then get's chained to the next call. Been
looking at Scala DSL's too long, but I think it is the patten you want
here; each step returns a wrapper class around the call to the
ResourceBuilder and state is retained in the wrapper instead of the
ResourceBuilder itself? May be too much refactoring, I've just started
looking at Sling...
On Saturday, December 12, 2015, Bertrand Delacretaz
wrote:
> Hi Peter,
>
> Good to read you here!
>
> On Fri, Dec 11, 2015 at 5:49 PM, Peter Hunsberger
> > wrote:
> > ...It's not clear why you even need the resetParent concept. Why not
> just
> > build the two sets of resources separately? Eg:
> >
> > p.resource("a/b");
> > p.resource("c/d"); ...
>
> The ResourceBuilder is stateful, to make it easy to create content
> hierarchies, so I think you need a way to tell it to restart at the
> top in some cases - or implement pop() to go back up the stack of
> created resources, but that makes it less intuitive IMO.
>
> But maybe you have better ideas on how to express this example tree in
> a fluent API?
>
> > ├── apps
> > │ ├── myapp
> > │ │ └── components
> > │ │ └── resource
> > │ │ ├── models.js
> > │ │ └── text.html
> > │ └── myapp.json
> > └── content (title:"foo")
> > ├── myapp
> > │ └── resource
> > └── myapp.json
>
> The current code for creating a similar tree is in
> ResourceBuilderImplTest.treeWithFiles() [1]
>
> -Bertrand
>
> [1]
> https://svn.apache.org/repos/asf/sling/trunk/bundles/commons/resourcebuilder/src/test/java/org/apache/sling/resourcebuilder/impl/ResourceBuilderImplTest.java
>
--
Peter Hunsberger
[jira] [Updated] (SLING-5357) [ext][sling pipes] documentation
[ https://issues.apache.org/jira/browse/SLING-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5357: --- Attachment: SLING-5357.patch please find the documentation patch > [ext][sling pipes] documentation > > > Key: SLING-5357 > URL: https://issues.apache.org/jira/browse/SLING-5357 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier >Priority: Minor > Attachments: SLING-5357.patch > > > Now SLING-5134, github documentation [0] should be migrated to Sling's site > [0] https://github.com/npeltier/sling-pipes/blob/master/README.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-5357) [ext][sling pipes] documentation
[ https://issues.apache.org/jira/browse/SLING-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054703#comment-15054703 ] Nicolas Peltier edited comment on SLING-5357 at 12/12/15 11:16 PM: --- please find the documentation patch (note that to be completely up to date, it should have SLING-5361 & SLING-5362 in) was (Author: npeltier): please find the documentation patch > [ext][sling pipes] documentation > > > Key: SLING-5357 > URL: https://issues.apache.org/jira/browse/SLING-5357 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Nicolas Peltier >Priority: Minor > Attachments: SLING-5357.patch > > > Now SLING-5134, github documentation [0] should be migrated to Sling's site > [0] https://github.com/npeltier/sling-pipes/blob/master/README.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [apachecms] contributing documentation for non commiters
Thanks Bertrand! it helps, actually used a mix of the online tool for previewing and svn diff for generating the patch > On 09 Dec 2015, at 11:30, Bertrand Delacretaz wrote: > > Hi, > > On Tue, Dec 8, 2015 at 10:02 AM, Nicolas Peltier wrote: >> ...So i basically added a mdtext file, and modified another with a link to >> it, ideally i’d only need to visualize >> the changes on those two files. Can someone tell me how to (simply) do >> this?... > > As per http://www.apache.org/dev/cmsref.html#non-committer has > instructions on how to do this, I haven't tested them. > > The CMS has its own flavor of markdown so you might not be able to > fully validate your content without it. But we can also slightly tweak > patches that you would provide, if needed. Let's not get in the way of > people who want to contribute docs ;-) > > -Bertrand
