fix: When you try to publish your final plugin a lot of undocumented steps are required

[rekire]

Description
Currently the generated flutter plugin works so far fine while development (except a couple of possible improvements like #42, #43, #44). However when you try to publish it at least as git dependency (as some kind of preview) you will notice quickly that there are a lot of "path: ../xyz" dependencies which simply won't work. This should be mentioned at least or might be some help how to manage this.

Steps To Reproduce

1. Create the flutter plugin
2. Add all the features you want
3. Try to add your plugin as a dependency in a flutter app

Expected Behavior
The plugin should work

Actual Behavior
The plugin cannot be resolved since the ".." dependencies are unknown.

[alestiago]

Hi @rekire thanks for opening this issue 🙌

I think you are referring to ".." dependencies as those path dependencies.

How are you adding the plugin into your flutter application?

[rekire]

Sorry for the late reply, right now I'm adding it as git dependency. But I'm right now on the way to publish it on pub.dev. Since I'm also changing my platform interface before the 1.0.0 I notices that tagging it with a real version makes it also more complicated since you need to keep in mind that the interface it has its own version. Hints for that might be good too

[alestiago]

When publishing to pub.dev it will most likely complain about path dependencies.

I recommend reading the official documentation for publishing, let me know if such documentation helps out.

I think it wouldn't hurt to include a "Publishing your plugin" section in the generated template within a "CONTRIBUTING" file based on the generation. Would you be interested in writing such documentation?