You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dan Klco (Jira)" <ji...@apache.org> on 2022/01/20 20:34:00 UTC
[jira] [Commented] (SLING-11078) Repoinit Parser - Describe and Validate Operation.asRepoInitString() Format
[ https://issues.apache.org/jira/browse/SLING-11078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479661#comment-17479661 ]
Dan Klco commented on SLING-11078:
----------------------------------
Pull request created: https://github.com/apache/sling-org-apache-sling-repoinit-parser/pull/16
> Repoinit Parser - Describe and Validate Operation.asRepoInitString() Format
> ---------------------------------------------------------------------------
>
> Key: SLING-11078
> URL: https://issues.apache.org/jira/browse/SLING-11078
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Affects Versions: Repoinit Parser 1.6.10
> Reporter: Dan Klco
> Assignee: Dan Klco
> Priority: Minor
> Fix For: Repoinit Parser 1.6.12
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There's no JavaDoc for Operation.asRepoInitString(), however all of the other operations follow the convention of using an OS-agnostic line separator at the end of the statement and this would seem like a reasonable safety measure for generating scripts.
> We should clarify the intended format in the JavaDoc and add a test to verify the behavior.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)