Angular - Allow UI generation for MS Services #18816
Description
Resolves #18646
This PR fixes the solution name declaration in AngularUiGenerateWithSchematicsCommand.cs supposing that we already have a library with the same name.
Checklist
- I fully tested it as developer / designer and created unit / integration tests
- I documented it (or no need to document or I will create a separate documentation issue)
- I worked with the design team to get their idea for UI/UX design (or no need to design for this PR)
- I've assigned reviewer, related labels and set a milestone for this PR
How to test it?
- You need to create a project with microservice template, then add a new service as explained here
- You should add a library for the angular application that would have the same name with the service you added.
- Once you generate an entity through Suite, all configurations will be managed under the angular app (since the suite will use the name of your solution as
MySolutionfromMySolution.MyNewService) - Based on this generation, you will need to take them back to your library to make the implementation work.
- You can also see an example app here
NOTE
Another problem to discuss is when we get the solution name as MyNewService by modifying the logic like this
if (_options.Solution.IsMicroserviceNolayerProject){
solutionName = _options.Solution.Name.Split('.')[1] + " ";
}
we can still use the application approach. However, this would also require more modifications beyond angular implementation and makes no sense out of using a library as it should be.
In any case, I believe this subject needs further discussion to get done. What do you think @masum-ulu 🙌🏻