Thank you!

[nandorojo]

This is exactly what I was looking for -- can't wait to try it out! Any thoughts on publishing the config plugin as an NPM package with docs?

[gaishimo]

Glad the repository was helpful to you.

I have no plans to make it an npm package at this time because the contents of the widget folder vary so much depending on what the developer wants to create that it would be difficult to make it generic.

However, it would be ideal if it were offered as a generic Config Plugin.

[nandorojo]

i think it’s actually pretty doable, i’ve gotten it to be pretty generic in my fork

[nandorojo]

i think the plug-in would be on npm, and then people would make their own widget folders

[gaishimo]

Sounds nice! It would be great if it could be a generic config plugin.

[nandorojo]

I opened a PR to make the plug-in more abstracted. The only other missing wins would be to:

1. let you override the widget directory, and
2. abstract the Info.Plist file into the config plugin

With those in mind, I think a withWidget() plugin could be published. Users would customize their own files inside of widget/

[tomhopkins]

Slightly off topic: really grateful for this excellent project which is working super well for me (only done iOS so far). Currently stuck on whether I can split up the widget.swift file as its c. 490 lines with a way to go. Can anyone point me in the right direction? I was thinking sub views could be individual files but it doesn’t compile.