Closed IRasmivan closed 2 months ago
This error was not in "com.disneystreaming.smithy4s" % "smithy4s-sbt-codegen" % "0.18.0"
version
This error was not in
"com.disneystreaming.smithy4s" % "smithy4s-sbt-codegen" % "0.18.0"
version
That's useful info, I'll do a bisect.
It's a regression from #1301.
Diff of 0.18.3 and 0.18.4:
14c14
< final case class CloudWatchEventsExecutionDataDetails(included: IncludedDetails = com.amazonaws.sfn.IncludedDetails(false))
---
> final case class CloudWatchEventsExecutionDataDetails(included: IncludedDetails = com.amazonaws.sfn.includedDetails(false))
24c24
< IncludedDetails.schema.required[CloudWatchEventsExecutionDataDetails]("included", _.included).addHints(smithy.api.Documentation("<p>Indicates whether input or output was included in the response. Always <code>true</code>\n for API calls. </p>"), smithy.api.Default(smithy4s.Document.fromBoolean(false))),
---
> IncludedDetails.schema.field[CloudWatchEventsExecutionDataDetails]("included", _.included).addHints(smithy.api.Documentation("<p>Indicates whether input or output was included in the response. Always <code>true</code>\n for API calls. </p>"), smithy.api.Default(smithy4s.Document.fromBoolean(false))),
so it's definitely default-related.
The datatype in smithy is named boolean includeDetails
, so we're probably not capitalizing it by accident in TypedNode rendering. I'll prepare a more minimal reproduction.
Description
I encountered an issue while adding the
aws-sfn-spec
dependency and enabling theSmithy4sCodegenPlugin
. The generated files seem to reference incorrect package members, causing compilation errors.Steps to Reproduce
Added the following dependency to my
build.sbt
:Enabled the Smithy4s plugin in my project:
Ran the SBT compile process.
Actual Behavior
During compilation, I encountered the following errors from generated code in the
src_managed/main/smithy4s
directory:Environment
0.18.23
2023.23.30
1.6.2
2.13