Feel free to add a PR, or @vlazdra may be interested in adding this.

This should be pretty straightforward, might be a good start as a first issue if you'd like to open a PR @petcupaula ? 😃

If not, let me know so I can extend this feature. 😃

@vlazdra Feel free to go ahead with it 😃

Ok. 😃

Just to be clear you'd like to have the ability to not specify the exact config file but instead provide the asterisks and for the tool to scan all the files and use all that were found as flavors and generate the splash screen for all of them? @petcupaula

That way, if you maybe have many flavors, you wouldn't need to specify the exact file names/flavor names and miss some, and in the future if you add new ones, you won't need to adapt the run script? Am I understanding you correctly on this?

Yes, exactly! A match on all files with the right prefix (flutter_native_splash*) and then splash screens are generated for everything defined in those files.

Hey @petcupaula I've made the PR for the changes that you desired.

Until Jon responds and approves them (or denies them), if you are willing to help and maybe give some feedback if the changes work, that would be awesome! 😃

To try out the changes in your project, you can add my fork and branch to your project like so:

  flutter_native_splash:
    git:
      url: https://github.com/vlazdra/flutter_native_splash
      ref: generate-all

Then do a flutter pub get and latter on run the command in your root: dart run flutter_native_splash:create --all-flavors

Please make sure you are working with a clean branch in your project. Do not run it if you have uncomited changes on your branch.