Fix for Ad-Hoc Case Class producing Dynamic Queries

[deusaquilus]

Fixes #992

Problem

Whenever Ad-Hoc case classes are used, AST produces a Dynamic Query which should not be the case.

Solution

Add case for Ad-Hoc Case Class in Unliftables.

Notes

Please note that I also added a test to IsDynamicSpec which is supposed to test this functionality but the IsDynamic method will produce a 'false' (i.e. it thinks it's not dynamic) even when line 154 in Unliftables in commented out. I think IsDynamic doesn't work properly but not sure what to do about it.

Checklist

• Unit test all changes
• Update README.md if applicable
• Add [WIP] to the pull request title if it's work in progress
• Squash commits that aren't meaningful changes
• Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

[mosyp]

@deusaquilus Thanks for contribution and sorry for missunderstanding =)
IsDynamic traverses a given ast to look for a Dynamic ast. But in your case that was a missing unliftables which actually tightly bound to macros itself and #191 confirms this - e.g. there's no way to test this (programmatically at least).

[deusaquilus]

Okay. Should I remove the test then?

[deusaquilus]

Well, you could theoretically call scala.tools.nsc.Main from SBT invoking a particular cp e.g:

-cp io.getquill.MyTest quill-sql/src/main/scala/io/getquill/MyTest.scala

... and then if you can somehow suck-in the compiler output you could check that the query string is present (or check that 'Dynamic Query' is not present). It would be more of an integration test then a unit test though.

[mosyp]

@deusaquilus good point on that sbt-specific approach!
Regarding PR, yes pelase remove this test

[fwbrasil]

I love the number of this PR! 💯0