A quick solution for ensuring that local changes made during development does not get overwritten when using the Flutterflow CLI.
Control the files or directories you do not wish to overrwrite when you pull code with the CLI tool.
Any file or folder in .flutterflowignore will not be overwritten when you run flutterflow-filtered-pull.
Download this project and put the flutterflow-filtered-pull file in the base of your local FlutterFlow project directory.
Requires rsync and flutterflow_cli to be installed on your machine and available in your path.
If you use gitbash, you can refer to install-rsync.sh to setup rsync on GitBash.
Before the first usage, you will need to make the file executable by running:
chmod +x flutterflow-filtered-pull
Then, add a .flutterflowignore file in the root of your project and treat it just like a .gitignore file. See the file in this directory as an example.
./flutterflow-filtered-pull --project <FlutterFlow Project ID> --token <FlutterFlow CLI Token> [--no-include-assets] [--branch-name <Branch Name>] [--endpoint <Endpoint>]
By default, the --include-assets and --no-parent-folder flags of the CLI tool are included in this operation, so files will be fetched directly into the current directory.
The simplest method to create the command is to copy and paste the CLI command from FlutterFlow and modify it slightly: remove flutterflow export-code and replace with ./flutterflow-filtered-pull.
