IAdmin | 基于laravel5.2的后台管理系统 - 基于laravel5

Registrations in IServiceCollection are key-value pairs, where the service (or abstraction) is the key and the component (or implementation) is the value. Lookup will be done based on that exact key. So in your case you only registered ICatalogService, and not IOperations. This means the IOperations can't be resolved. You will have to register IOperations explicitly. For instance:

Change your return statement like

The question is - why it is saved when upcasted?

Because casting doesn't change the object at all. It just changes how you're viewing the object.

Think of it like being a person. You may have different ways that people can view you:

• A colleague
• A manager
• A family member
• A friend

They only "see" certain aspects of you, but that doesn't change who you are.

Likewise a simple reference conversion doesn't change the object. If you call user.GetType() it will still report the actual type of the object. It's just that when you view the object through a particular lens (whether that's an interface or a base class) you only see the members that lens shows you.

(Note that a cast that calls a user-defined conversion, e.g. casting from XElement to string, is entirely different. That returns a reference to a new object, rather than just regarding the existing object in a different way.)

If you only want to see the IUser properties, use typeof(IUser).GetProperties() instead of calling GetType() first:

You have a design problem, i recommend you read about SOLID principles in the following link:

https://scotch.io/bar-talk/s-o-l-i-d-the-first-five-principles-of-object-oriented-design

In a correct design, you should not at all implement an interface if you will not implement one of its methods (the readAll i your case). this means you are mixing concerns, and your interface must be split into smaller interfaces. perhaps splitting the readall into a separate interface will solve your problem. for example, instead of ICrud, create an interface for write operations alone, and one for read operations, and one for readAll.

there is many ways to solve your problem preserving the interface ICrud as is, such as using object as a retrun type, or generics or dynamics. but what solves your problem from its roots is following a good design as i mentioned above.

Your answer is one word. Use Ad hoc polymorphism, which means you can have multiple methods of createAgentAccount, then in each of them call an other method to handle the details.

UPDATE This is what I think you want

There is a difference between roles and dynamic roles/states ($everyone and $authenticated), while your roles get stored in a table to keep the association with the user $everyone and $authenticated is just a state of the user. Look at a table named "RoleMapping", if that is correct. Also if you have a custom Role, create a custom RoleResolver.

There is really good documentation, and really not that hard to get started in Loopback 3.

https://loopback.io/doc/en/lb3/Defining-and-using-roles.html

This example gave me a great understanding of roles in general:

https://github.com/strongloop/loopback-example-access-control/blob/master/server/boot/role-resolver.js

It's an entire project so you can check out the models there aswell.

Try the below solution.Hope this will help you.