The current approach of having the importer as a subdirectory within flutter_scene is a flawed uphill battle. All of Flutter's tooling (pub, analyzer, formatter) operate on directories, and so a bunch of exclusion rules and hacks need to be maintained in order to make them work properly.
In the future, this repository will likely contain more packages as well as utilities for a doc site. So instead, the flutter_scene and flutter_scene_importer packages should be separate directories, preferably following the conventional milos structure.
The current approach of having the importer as a subdirectory within flutter_scene is a flawed uphill battle. All of Flutter's tooling (pub, analyzer, formatter) operate on directories, and so a bunch of exclusion rules and hacks need to be maintained in order to make them work properly.
In the future, this repository will likely contain more packages as well as utilities for a doc site. So instead, the
flutter_sceneandflutter_scene_importerpackages should be separate directories, preferably following the conventional milos structure.