sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Peltier (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-7013) PipesBuilder API is too rigid
Date Tue, 29 Aug 2017 19:59:00 GMT

     [ https://issues.apache.org/jira/browse/SLING-7013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nicolas Peltier resolved SLING-7013.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Pipes 1.0.4

fixed in https://svn.apache.org/viewvc?view=revision&revision=r1806636
- didn't add writer (makes no sense as it's tied to servlet),
- didn't add complicated structure handling, as it can be added later on if needed without
updating the API, now "with" is more flexible


> PipesBuilder API is too rigid
> -----------------------------
>
>                 Key: SLING-7013
>                 URL: https://issues.apache.org/jira/browse/SLING-7013
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Nicolas Peltier
>            Assignee: Nicolas Peltier
>             Fix For: Pipes 1.0.4
>
>
> Some things are missing from Pipes API and there is no workaround:
> # additional bindings,
> # writers,
> # async
> # complicated structures (for write, filters, ...) 
> # any other parameter i forgot
> after trying it groovy + pipebuilder is rather cool UI to generate & test pipes,
so would be cool to have everything pipes can do
> as i don't want any of the above enhancement to trigger a major bump in the version,
i'd like to do that change for 1.0.x



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message