Hi guys! Could you give me some feedbacks about an...

# arrow-meta

[bloder]

Hi guys! Could you give me some feedbacks about an idea, please? The idea is basically create a new transform to enable tests, basically a more typed solution for testing, and now as we can combine transformations this is totally possible:

private val Meta.transformTest: Plugin
  get() = "Transform Test" {
    meta(
      classDeclaration({ name == "ManyCustomCase" }) { c ->
        (Transform.replace(...)
        + Transform.remove(...)
        + Transform.newSources(...)
        + Transform.enableTest())
      }
    )
  }

With that we don't need to write a comment in our transformed code to generate .meta files. (and of course this idea wasn't created because I always forget to put the test comment 😅)

[raulraja]

This is great but it’s unrelated to test since meta debug is used for other things too.
//metadebug supports a set of commands to print out dates etc.
I would just call this Transform.debug and it takes 0 to N commands as supported by the test DSL.

[bloder]

I think we already have a debug transform planned, no?