You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Diamond dependency issue causes huge blowup in size of fully-resolved files. Would be awesome if those were instead small and readable. This could be something we could work around using the existing Haskell API.
Deserialising existentials. Even though, without --system-device, we don't care what the type of axis and event data is, we can't accept a Layout Axis Key - it has to be a Layout {} {}. This is really awkward.
When all that's done, we can set up #7, and announce in a few places (r/madeinhaskell? hacker news?).
We can also release on Hackage, with the pre-compiled JS from Elm etc. Though we'll have to have a think about how we handle the platform-specific default.dhall, and the release flag.
The text was updated successfully, but these errors were encountered:
--system-device
, we don't care what the type of axis and event data is, we can't accept aLayout Axis Key
- it has to be aLayout {} {}
. This is really awkward.We probably need Monoid law broken withEDIT: It's fine, we work around this safely in d9929bdExceptT
and parallel composition composewell/streamly#1203 fixed, especially when it comes to releasing as a library and exposingServerConfig.onUpdate
. For the executable, it's possible we only use it safely, aside from the error handling issues.When all that's done, we can set up #7, and announce in a few places (r/madeinhaskell? hacker news?).
We can also release on Hackage, with the pre-compiled JS from Elm etc. Though we'll have to have a think about how we handle the platform-specific
default.dhall
, and therelease
flag.The text was updated successfully, but these errors were encountered: