softwaremill / softwaremill/tapir

[BUG] method `schemaForCaseClass` is declared as erased, but is in fact used

Open
#1,731 4 comments 3 reactions 1 assignee View on GitHub

@kubinio123 is already working on this.

Since Jan 14, 2022.

Dominant language
Scala
Stars
1.5k
Forks
468
Avg merge
5h 37m
Merged PRs (30d)
34

Description

Tapir version: 0.19.1+

Scala version: 3.1.0

Describe the bug

What is the problem?
mysterious compile errors

method isValueClass is declared as erased, but is in fact used
method isObject is declared as erased, but is in fact used
method schemaForCaseClass is declared as erased, but is in fact used
method anns is declared as erased, but is in fact used
method typeInfo is declared as erased, but is in fact used
method typeAnns is declared as erased, but is in fact used
method getParams is declared as erased, but is in fact used
method summon is declared as erased, but is in fact used

How to reproduce?

Maybe you can provide code to reproduce the problem?
https://scastie.scala-lang.org/Fy5fl0keRXWtP8i5bSCymA

Additional information
If reduce field numbe of case class StandardAreaInfo or TwinNode by 1,for example, comment country:String or city:String, or realSceneID:UUID or coverImage:Option[String] , the errors disappears

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.