Is your feature request related to a problem? Please describe.
Since it is quite an effort to create an Elm compiler for morphir-scala and morphir-dotnet, those ecosystems rely on morphir-elm for the Elm to Morphir IR toolchain.
Both are targeting to integrate their tooling by enlisting the morphir-elm tooling and invoking morphir-elm as a subprocess.
It would ease integration if there was a mode where instead of creating files morphir-elm make just wrote the file text to stdout so that morphir-scala and morphir-dotnet can wrap their own processing actions around the various JSON files produces (primarily morphir-ir.json).
Describe the solution you'd like
Provide a --no-files or some equivalent flag which would put the CLI in a mode where the following occurs:
All errors and warnings would print to stderr not stdout (I feel like this should be the default of the CLI anyways)
All JSON output that would be written to files are emitted to stdout.
A simple YAML Header should be added prior to the JSON to allow metadata like target file names to be communicated over stdout
Describe alternatives you've considered
An alternative would be to communicate this info using JSON RPC or GRPC but that is a lot of work and this solution should serve most needs.
Is your feature request related to a problem? Please describe. Since it is quite an effort to create an Elm compiler for
morphir-scala
andmorphir-dotnet
, those ecosystems rely onmorphir-elm
for the Elm to Morphir IR toolchain.Both are targeting to integrate their tooling by enlisting the
morphir-elm
tooling and invokingmorphir-elm
as a subprocess.It would ease integration if there was a mode where instead of creating files
morphir-elm make
just wrote the file text to stdout so thatmorphir-scala
andmorphir-dotnet
can wrap their own processing actions around the various JSON files produces (primarily morphir-ir.json).Describe the solution you'd like Provide a
--no-files
or some equivalent flag which would put the CLI in a mode where the following occurs:Describe alternatives you've considered An alternative would be to communicate this info using JSON RPC or GRPC but that is a lot of work and this solution should serve most needs.
Additional context N/A