You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I noticed you decided to describe from and to classes in the AsMapper attribute
But instead of it you could also define abstract static methods (getFrom, getTo) where you return the same static info
abstract static protected function getFrom(): string;
abstract static protected function getTo(): string;
😏I just was wondering if there is a special idea to use AsMapper instead of describing in in the static mehtods of the interface?
I really hope you'll answer to me😁
Maybe because you assign "micro_mapper.mapper" to the created service. And particularly cuz of this you made up your mind to use the attribute called As*
But as we all know we could use thr following to assign a tag relying on the interface:
As I noticed you decided to describe from and to classes in the AsMapper attribute
But instead of it you could also define abstract static methods (getFrom, getTo) where you return the same static info
😏I just was wondering if there is a special idea to use AsMapper instead of describing in in the static mehtods of the interface?
I really hope you'll answer to me😁
Maybe because you assign "micro_mapper.mapper" to the created service. And particularly cuz of this you made up your mind to use the attribute called As*
But as we all know we could use thr following to assign a tag relying on the interface:
Or it's just a question of humans' taste
The text was updated successfully, but these errors were encountered: