Refactoring routes about project-avocado HOT 5 CLOSED

I am not really sure of this implementation. Imagine the home screen which is the gateway to all other screens. In this, it'll have to refer each of the class to get its route. Won't having one route utility file be better?

CC: @Thesmader

Ok, so creating a class named routes, adding all the static const strings under that and just calling the routes class wherever required would be better maybe?
That way, instead of referring to all the classes, it can just refer to the routes class and tap into the required route.

from project-avocado.

If I understand correctly, we will have a utility file which will manage the routes. Isn't it?

Sounds like something that will improve the codebase

from project-avocado.

Not exactly. I basically added

If I understand correctly, we will have a utility file which will manage the routes. Isn't it?

Sounds like something that will improve the codebase

Not exactly, I created a static const String (id) in every page which stores the name of the route. So you can easily tap into the route by using something like HomePage.id.

from project-avocado.

@DesignrKnight Please assign this to me. I would like to work on it.

from project-avocado.

I am not really sure of this implementation. Imagine the home screen which is the gateway to all other screens. In this, it'll have to refer each of the class to get its route. Won't having one route utility file be better?

CC: @Thesmader

from project-avocado.