breautek commented on issue #1256:
URL: https://github.com/apache/cordova-ios/issues/1256#issuecomment-1244681699
> options=":sources => [ 'my_source' ]"/>
I think this would be incredibly tedious to author.. especially if there are
several options involves or several values that needs to be set. Instead I
think we should probably favour a more declarative approach and have a
parser/reader build out the podfile string.
I don't really know enough about pods to suggest something that could be
powerful enough to handle wide range of options, but given the `:<optionName>
=> [ values...]` syntax, it could look something like this:
```xml
<podspec>
<plugins>
<plugin name="myPluginName">
<option name="sources">
<!-- If pods supports different data types, then we could
use more explicit tags like <string> or <number>, etc.
-->
<value>my_source</value>
<value>my_other_source</value>
</option>
</plugin>
<plugin name="myOtherPlugin" />
</plugins>
</podspec>
```
I've made an assumption that option values are comma delimited strings, and
I assume if there were more than one option, then they will be comma delimited
as well, but the above would be a more declarative approach to handling the
options so that you don't need to escape or make use of HTML entities for
quotations or other potentially conflicting symbols, what do you think?
```
plugin 'myPluginName', :sources => [ 'my_source', 'my_other_source' ]
plugin 'myOtherPlugin'
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
