Edouard Marquez

Thanks a lot for your answer. What about prefixing this kind of file? And maybe make this one configurable?

@monsieurtanuki That's exactly what you've described. I think I will list all the possible routes before starting anything. I know, this will take some time to develop, but when it...

I am not fully sure that it would be a nice idea to have the same routes, as the navigation within the app will be different. Basically, it's the same...

Yes, I will (re)work on it ASAP. This feature was judged non essential for the initial release, but now it is

So you're right. Let's we rename the current `smooth_app` to `common` (but we can keep the same name). Since it's not the root package anymore, we HAVE TO link all...

If you download a dependency from pub.dev and this dependency have some assets, you have to specify the `package` entry. Otherwise Flutter won't know which file to take. > and...

If you want to better understand why, just decompile an Android APK and you will thus understand that `package` question

Let me rephrase everything. Let's say we have: - A base app - A dependency (cupertino_icons for example) When in your base app, you say Image.asset(path), it automatically implied package...

No, what I just say, is: - Assets from the base app = accessible with or without specifying the package - On all cases, specify the name of the package...

You're right @M123-dev, before handling deep links, we have to migrate the app named routes or Navigator 2. I create a separate issue for migration.