proposal: support custom scripts about mason HOT 5 CLOSED

Few remarks:

1. Security - this feature allows for execution of arbitrary code on the user's machine. If implemented, we should clearly notify the user and ask for approval when running any script that is not maintained by us
2. I see the resemblance to the git hooks and maybe hooks could be a more natural name for them? Then either pre-build or pre_build hooks would be present in the hooks directory
3. There should be a way to skip and approve running the scripts in a headless mode e.g. --skip-script-approval and --skip-scripts or similar

from mason.

Thanks for the quick feedback @orestesgaolin! 🙏

1. Security - this feature allows for execution of arbitrary code on the user's machine. If implemented, we should clearly notify the user and ask for approval when running any script that is not maintained by us

I was hesitant about this from a security standpoint as well but after thinking about it it's really not much different than installing a dart package from pub.dev and running it on your machine. I think we should expect that developers evaluate the bricks they choose to use and use discretion when it comes to what they install/run on their machine.

2. I see the resemblance to the git hooks and maybe hooks could be a more natural name for them? Then either pre-build or pre_build hooks would be present in the hooks directory

I like that suggestion and I'm happy to rename to hooks and use pre_build instead of pre_gen 👍

3. There should be a way to skip and approve running the scripts in a headless mode e.g. --skip-script-approval and --skip-scripts or similar

Yup, completely agree!

from mason.

Kind of off topic,

But I use mason to assemble basiclly from express , next, flutter,
db , even firestore + ansible

So load of bricks

The problem I ran into is those appending those scripts in

package.json

pubspec.yaml is a mess

Can we just do package.json inside of flutter project.

something like

"scripts": {
    "assmeble": "mason assemble ."
}

That just the end goal , it brings in all those line in info.plist , gradle,

from mason.

Kind of off topic,

But I use mason to assemble basiclly from express , next, flutter, db , even firestore + ansible

So load of bricks

The problem I ran into is those appending those scripts in

package.json

pubspec.yaml is a mess

Can we just do package.json inside of flutter project.

something like

"scripts": {
    "assmeble": "mason assemble ."
}

That just the end goal , it brings in all those line in info.plist , gradle,

You should be able to use something like derry to manage scripts in your pubspec.yaml similar to a package.json. Hope that helps 👍

from mason.

This is closed by #153 and is available in mason v0.0.1-dev.57 🎉

from mason.