Integrate IOGX #44
Integrate IOGX #44
Conversation
There was a problem hiding this comment.
I tried local development and I was able to setup the backend and fronted without too much problem.
The only change that I ask is to update this documentation as we are switching from plain std to iogx
Also, I defer to @shlevy to check the ci/deployment part
|
|
||
| { | ||
| modules = [{ | ||
| packages.marlowe-symbolic.ghcOptions = [ "-Werror" ]; |
There was a problem hiding this comment.
Why do we have these here instead of in cabal.project? @hrajchert
There was a problem hiding this comment.
This is common to all repos. Basically we want -Werror in CI, but not locally
There was a problem hiding this comment.
OK. Might be nice to have some way to do this behind the scenes. E.g. ask haskell.nix "which packages in this package set were actually defined as top-level in the cabal.project?" and turn on Werror for all of those.
As part of the ongoing effort to build a Developer Platform for IOG, the smart-contracts-dev-empowerment team is releasing IOGX - a Flake Template for Haskell Projects at IOG
The vision of IOGX is to provide a JSON-like, declarative interface to Nix, so that developers unfamiliar with the language may independently maintain and add to the Nix sources with minimum effort.
The goal is to integrate with all Smart Contracts repositories, and maybe more.
There are currently 8 repositories using this, including marlowe-cardano.
As developers nothing changes for you: you will enter nix develop and you will get into a new shell.
There might be some rough edges but we will be prompt to smooth them.
Notable changes that might require review: