Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix for square brackets in the operation name #32

Merged
merged 6 commits into from
Jun 4, 2019
Merged

Fix for square brackets in the operation name #32

merged 6 commits into from
Jun 4, 2019

Commits on Jun 4, 2019

  1. Fix for square brackets in the operation name 

    The generator is broken for operations with parameters that have square
brackets in the name. Apparently the version of Swagger Codegen that
we're using is not excluding `[` and `]` when doing the camelization of
the parameter name.

Fixes #31
    @cortinico
    cortinico committed Jun 4, 2019
    Configuration menu
    Copy the full SHA
    dfbf16d View commit details
    Browse the repository at this point in the history

  2. Preparing version 1.1.0-SNAPSHOT 

    We need to bump the version to a -SNAPSHOT in order to be able to test
the upcoming changes.
    @cortinico
    cortinico committed Jun 4, 2019
    Configuration menu
    Copy the full SHA
    5d27798 View commit details
    Browse the repository at this point in the history

  3. Add the junit-tests module inside the samples. 

    Creating the `junit-tests` sample to have a space where we can test our
specs and make sure we cover all the edge cases reported in bug reports.
    @cortinico
    cortinico committed Jun 4, 2019
    Configuration menu
    Copy the full SHA
    5e983bc View commit details
    Browse the repository at this point in the history

  4. Add juni-tests to the Samples section in the README

    @cortinico
    cortinico committed Jun 4, 2019
    Configuration menu
    Copy the full SHA
    1b67db3 View commit details
    Browse the repository at this point in the history

  5. Add conditional plugin loading in the settings.gradle.kts file 

    Travis is not able to build the project as the Gradle plugin
1.1.0-SNAPSHOT is missing in all the repository. This is preventing the
project from even building the plugin and publishing it to Maven Local.

To avoid this, I'm adding a conditional loading of the Gradle modules
that will load the `samples` only if we the plugin is found in any
repository.
    @cortinico
    cortinico committed Jun 4, 2019
    Configuration menu
    Copy the full SHA
    4af82ed View commit details
    Browse the repository at this point in the history

  6. Adding JUnit tests for removeNonNameElementToCamelCase

    @cortinico
    cortinico committed Jun 4, 2019
    Configuration menu
    Copy the full SHA
    d5b95f1 View commit details
    Browse the repository at this point in the history