Remove samples/generated-code as it is duplicated by junit-tests #89
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is created as result of #86 conversation.
The generated-code samples are not much different than groovy-android sample except for the fact that it did contain the generated code. Unfortunately, we were not building, testing or more in general doing something with the code so it was there mostly as a sort showcase of the generator output.
As junit-tests does actually run tests on the generated code, and does include the plugin generated code we might just remove the
samples/generated-code
by hinting (on the README) the presence ofsamples/junit-tests
as an example of the generated code.Additionally to that the junit-tests sample does provide a possible implementation of integration tests that allow to verify the behaviour of the APIs and Models.