This is kinda disappointing actually. If you don't want to use the hack wherein there is a hashtag at the beginning of a route you have to instead make 404 errors at your server reroute to your token .html page. I'm serious. Kinda ghetto, huh? It makes sense right? If you go to a route and it's just not there, how else can you communicate the route to your Angular 4 app hosted at what is honestly a completely different route as far as your hosting is concerned?
No comments:
Post a Comment