Closed jrkd closed 2 years ago
Left few notes in the PR, however you should create a PR to the vNext branch, with the latest changes. There are also no tests for the functionality.
Ive updated as requested, and changed the merge target to vNext.
As for the tests, could you direct me to where tests should be placed in this project?
Left few notes in the PR, however you should create a PR to the vNext branch, with the latest changes. There are also no tests for the functionality.
Ive updated as requested, and changed the merge target to vNext.
As for the tests, could you direct me to where tests should be placed in this project?
Hi @jrkd, I've looked over the changes but I think changing the target branch will not be enough. You should first resolve merge conflicts or checkout the vNext branch locally and make these changes there (I think this might be easier, because there are lot of breaking changes in the project structure). Tests which should be edited can be found in the https://github.com/Kentico/kontent-generators-net/tree/vNext/test/Kentico.Kontent.ModelGenerator.Tests/Generators.
Closing. The original issue #141 will be fixed by #147. Thanks for the activity @jrkd.
BaseClassCodeGenerator/ClassCodeGenerator/TypeProviderCodeGenerator
ClassCodeGenerator
Motivation
Fixes #141
Checklist
How to test
Run the generator, and view the top of each file.