Fix #339: support useTimeType and common spec fields in Gradle AsyncAPI plugin (6.7.3) - #412
Merged
jemacineiras merged 2 commits intoAug 16, 2026
Conversation
… AsyncAPI plugin (6.7.3)
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
jemacineiras
self-requested a review
August 16, 2026 21:16
jemacineiras
previously approved these changes
Aug 16, 2026
jemacineiras
approved these changes
Aug 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #339
Problem
The Gradle AsyncAPI plugin failed with
Could not set unknown property 'useTimeType' for object of type com.sngular.api.generator.plugin.model.OperationParameterwhen configuringuseTimeType(ordateFormat,dateTimeFormat,useLombokModelAnnotation,modelNamePrefix) insideconsumer/supplier/streamBridge.OperationParameter.groovyonly exposedids,apiPackage,modelPackage,modelNameSuffix,classNamePostfix, andAsyncApiTask.toOperationParameterObjectonly mapped those — even though the engine'sOperationParameterObject(which extendsCommonSpecFile) supports all these fields, the docs document them, and the OpenAPI Gradle plugin already maps them (OpenApiTask.toFileSpec).Fix
scs-multiapi-gradle-plugin/.../model/OperationParameter.groovy: addedmodelNamePrefix,dateFormat,dateTimeFormat,useTimeType(TypeConstants.TimeType) anduseLombokModelAnnotation, mirroringCommonSpecFile.scs-multiapi-gradle-plugin/.../AsyncApiTask.groovy:toOperationParameterObjectnow maps the new fields ontoOperationParameterObject.ScsMultiApiTest.java: added 4 tests —useTimeTypemapping (ZONED), default (LOCAL), and mapping of the remaining common spec fields..codacy.yml: addedOperationParameter.groovytoexclude_paths, consistent with the other Gradle DSL model classes (*SpecFile.groovy,*Task.groovy) that are already excluded because CodeNarc's default rules (e.g. 4-spaceIndentation, missing Javadoc) flag this project's 2-space Groovy convention as noise.Validation
scs-multiapi-gradle-plugin:gradlew testgreen — 7 tests, 0 failures (was 3).multiapi-engine: full suite green — 133 tests, 0 failures.OperationParameter.groovyare the known Indentation/Javadoc-style noise; the file is now excluded like its siblings).