Use Relative Paths instead of fully qualified.

[rodydavis]

https://stackoverflow.com/questions/22764330/syntax-for-specifying-file-path-relative-and-absolute

This makes it a lot easier for reusable code in other projects.

Here is a plugin in vs code that does this already: https://marketplace.visualstudio.com/items?itemName=luanpotter.dart-import

[rodydavis]

instead of:

// STARTER: import - do not remove comment
import 'package:my-project/ui/contacts/contacts_screen.dart';
import 'package:my-project/ui/contacts/edit/contacts_edit_vm.dart';
import 'package:my-project/ui/contacts/view/contacts_view_vm.dart';
import 'package:my-project/redux/contacts/contacts_actions.dart';
import 'package:my-project/redux/contacts/contacts_middleware.dart';

use:

// STARTER: import - do not remove comment
import 'ui/contacts/contacts_screen.dart';
import 'ui/contacts/edit/contacts_edit_vm.dart';
import 'ui/contacts/view/contacts_view_vm.dart';
import 'redux/contacts/contacts_actions.dart';
import 'redux/contacts/contacts_middleware.dart';

and in a file you can go up folders:
import '../../redux/contacts/contacts_actions.dart';

[hillelcoren]

Maybe, not sure..

When we started with Flutter (around 6 months ago) I ran into problems using relative paths (ie, dart-lang/sdk#32916) and found always using the full path easier to work with. Additionally, this change would cause problems for people who used the older version of this project.

I'll keep it in mind if we release a v2 of the project.

[rodydavis]

Sounds good. As a final result, it is really helpful to copy files between projects. But performance may need to be more important here.