[ 
https://issues.apache.org/jira/browse/CB-13744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320238#comment-16320238
 ] 

ASF GitHub Bot commented on CB-13744:
-------------------------------------

jcaron23 commented on issue #12: CB-13744: Recognize storyboards as XML files
URL: https://github.com/apache/cordova-common/pull/12#issuecomment-356602756
 
 
   Extra commits reverted & title updated to include Jira issue number.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Handle storyboards as XML files
> -------------------------------
>
>                 Key: CB-13744
>                 URL: https://issues.apache.org/jira/browse/CB-13744
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: cordova-common
>            Reporter: Jacques Caron
>            Priority: Minor
>
> When editing a file with <config-file> or <edit-config>, only a few 
> extensions are recognised as XML, the rest are considered plists.
> The CDVLaunchScreen.storyboard generated by cordova-ios is XML. To be able to 
> edit it from config.xml, .storyboard files need to be recognised as XML.
> Pull request: https://github.com/apache/cordova-common/pull/12
> It may make sense to take this further, and either:
> - reverse the test, and only consider .plist files to be plists, and the rest 
> XML. Not sure if that could break something
> - or add an attribute to <config-file> and <edit-config> to specify the type 
> of file (XML or plist).
> However for the purposes of modifying the storyboard the (very minor) change 
> in the pull request is enough.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to