[jira] [Updated] (SLING-5729) pipe expressions should allow regexp with {n} or {n,m}

2016-10-10 Thread Oliver Lietz (JIRA) 

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

Oliver Lietz updated SLING-5729:

Affects Version/s: (was: Pipes 0.0.10)

> pipe expressions should allow regexp with {n} or {n,m}
> --
>
> Key: SLING-5729
> URL: https://issues.apache.org/jira/browse/SLING-5729
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Nicolas Peltier
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: Pipes 0.0.10
>
> Attachments: SLING-5729.patch
>
>
> expressions like
> {Code}
> ${(new Regexp('/foo/bar/./../.{8}').test(path)}"
> {Code}
> can't work right now because of the rather simple regexp for extracting them



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5729) pipe expressions should allow regexp with {n} or {n,m}

2016-06-21 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert updated SLING-5729:
--
Affects Version/s: Pipes 1.0.0
Fix Version/s: Pipes 1.0.0

> pipe expressions should allow regexp with {n} or {n,m}
> --
>
> Key: SLING-5729
> URL: https://issues.apache.org/jira/browse/SLING-5729
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Pipes 1.0.0
>Reporter: Nicolas Peltier
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: Pipes 1.0.0
>
> Attachments: SLING-5729.patch
>
>
> expressions like
> {Code}
> ${(new Regexp('/foo/bar/./../.{8}').test(path)}"
> {Code}
> can't work right now because of the rather simple regexp for extracting them



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5729) pipe expressions should allow regexp with {n} or {n,m}

2016-06-21 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert updated SLING-5729:
--
Component/s: Extensions

> pipe expressions should allow regexp with {n} or {n,m}
> --
>
> Key: SLING-5729
> URL: https://issues.apache.org/jira/browse/SLING-5729
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Pipes 1.0.0
>Reporter: Nicolas Peltier
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: Pipes 1.0.0
>
> Attachments: SLING-5729.patch
>
>
> expressions like
> {Code}
> ${(new Regexp('/foo/bar/./../.{8}').test(path)}"
> {Code}
> can't work right now because of the rather simple regexp for extracting them



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5729) pipe expressions should allow regexp with {n} or {n,m}

2016-05-15 Thread Nicolas Peltier (JIRA) 

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

Nicolas Peltier updated SLING-5729:
---
Attachment: SLING-5729.patch

failing tests + fix (enhancement of the regexp used for extracting expressions) 
in attached patch

> pipe expressions should allow regexp with {n} or {n,m}
> --
>
> Key: SLING-5729
> URL: https://issues.apache.org/jira/browse/SLING-5729
> Project: Sling
>  Issue Type: Bug
>Reporter: Nicolas Peltier
>Priority: Minor
> Attachments: SLING-5729.patch
>
>
> expressions like
> {Code}
> ${(new Regexp('/foo/bar/./../.{8}').test(path)}"
> {Code}
> can't work right now because of the rather simple regexp for extracting them



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)