There's no unit that encapsulates the logic around generating a full OData link, so tests end up integration style. Having an odata link factory abstraction allows unit testing such code.
We are putting two related properties together on the request: path handler and route name. These are a pair, which is a code smell that there's one abstraction here that should be used instead. Having an odata link factor also solves this problem.
We are putting two related properties together on the request: path handler and route name. These are a pair, which is a code smell that there's one abstraction here that should be used instead. Having an odata link factor also solves this problem.