Attila Mihaly

By the way this is how I implemented the OO rule last week: https://github.com/finos/morphir-elm/blob/3e8dcf5718c623417f6a1f01d4ffaad29f20ea6a/src/Morphir/Scala/Backend.elm#L334

So what's the conclusion here? As I'm reading through this again I'm reminded that all this rearranging will have a significant impact on the call-site especially if the functions are...

Can we represent a URL as a custom type in user code? Something like this: ```elm type alias URL = { scheme : Scheme , authority : Authority , path...

Thanks for raising these issues. We'll be looking into fixing these in the next couple of weeks.

The fix here is to add type ascriptions to every occurrence of type constructors to reproduce the semantics of Morphir in Scala. Here's how that looks like in the above...

One correction to the first bullet-point: We want the Spark AST to represent Spark group-by and aggregation operations, not the Aggregation API in the Morphir SDK. The rest looks correct.