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 a developer, I want to be able to generate boilerplate code without errors and a documentation should work as expected.
Actual behavior
The devon4net Cobigen Guide instructs the user to run the command dotnet new Devon4NetAPI. It will install the templates that will be used for the generation.
The directory name Devon4Net.Application.WebAPI.Implementation differs from the name used in the dotnet template that is going to be called by Cobigen.
This behavior can be changed to achieve a semi-expected result by renaming the installed directory name to Devon4Net.WebAPI.Implementation but it doesn't change the fact that the project has lots of wrong imports and errors.
The templates used by Cobigen have been modified to be fully aligned with the current version of devon4net.
A new pull request has been opened with these changes, when approved and merged with the main Cobigen branch the problem will be fixed. PR link: devonfw/cobigen#1621
Expected behavior
As a developer, I want to be able to generate boilerplate code without errors and a documentation should work as expected.
Actual behavior
The devon4net Cobigen Guide instructs the user to run the command
dotnet new Devon4NetAPI
. It will install the templates that will be used for the generation.The directory name
Devon4Net.Application.WebAPI.Implementation
differs from the name used in the dotnet template that is going to be called by Cobigen.This behavior can be changed to achieve a semi-expected result by renaming the installed directory name to
Devon4Net.WebAPI.Implementation
but it doesn't change the fact that the project has lots of wrong imports and errors.Take a look at my comment in devonfw/cobigen#1442 (comment) for more information.
Steps to reproduce (bug) / Use Case of feature request (enhancement)
You can use the images for the documentation and as a reference to reproduce this issue that I put together in devon4net doc.zip.
Related/Dependent Issues
#152
The text was updated successfully, but these errors were encountered: