Do not access the route directly from components about vue-realworld-example-app

[igeligel]

I also see it the same as you. Just views should access the $route. Components are just there for displaying data and handling state.

Would be fine if you tag it somewhere in the readme or in a similar place.

[alexandru-dodon]

@morficus aren't views meant to be tightly coupled to a particular application? This would make sense only in re-usable view components that ship as part of a package, for example. Well, that's just my opinion.

I'm available to fix this issue if it needs to be fixed.

[morficus]

@techiedod I could live with that.
I'm a fan of the "views" vs "components" separation. Makes a lot of sense to state that a particular "view" is intended to be tightly coupled with a particular route, in which case using this.$route would be fair game. But it should never directly outside of views (aka: anything under the "components" directory).

I just did a quick search in the "components" directory and it didn't find any uses of this.$route, so things look good in that regard 👍

(so assuming others agree) It would just need to document somewhere where and why accessing this.$route directly is acceptable.

PS: sorry for the delay in my reply. I have a kind of erratic schedule due to the holidays and all that :-p