[ComplianceTests] Malformed compliance tests#861
Conversation
# Conflicts: # modules/compliance-tests/src/smithy4s/compliancetests/ComplianceTest.scala # modules/compliance-tests/src/smithy4s/compliancetests/internals/ClientHttpComplianceTestCase.scala # modules/compliance-tests/src/smithy4s/compliancetests/internals/ServerHttpComplianceTestCase.scala # modules/transformers/src/SimpleRestJsonProtocolTransformer.scala
|
|
way to dig up an old issue, I know... the problem is that you're using a Java class: |
|
@kubukoz can you explain more. |
Sort of. The Scala standard library does call out to some Java classes/methods, but because Java code can't be transpiled to JS/Native, these classes/methods have to be reimplemented in Scala - you can find that e.g.
just because Scala.js and Scala Native's compiler plugins can only output the appropriate SJSIR / NIR files from Scala files. These *IR files are needed for further processing, e.g. linking and generating output JS/LLVM. to sum up, you can't use any Java symbol on JS/Native, unless a Scala implementation is also provided. This is why we have platform-specific files in the first place - sometimes you can't / don't want to reimplement the Java, so:
|
|
There was a project that provided a Java frontend for Scala.js, which would allow using Java code on the JS side here, but it seems to have been forgotten: https://github.com/arthanzel/scalajs-jfe |
|
closed in favor of #1918 |
This pr adds the last component of the protocol compliance tests as defined by Smithy
https://smithy.io/2.0/additional-specs/http-protocol-compliance-tests.html#httpmalformedrequesttests