colin-lamed
colin-lamed
Any reason why the discarding variants `forM_` and `mapM_` have been replaced by the monomorphic variant? ``` ClassyPrelude> :t mapM mapM :: (Traversable t, Monad m) => (a -> m...
This is related to #170
I'll just add some thoughts on this. One goal is to support this without choosing a particular standard, or confining an organizations interpretation of one. Some HATEAOS standards: * [HAL](http://stateless.co/hal_specification.html)...
Is there any intention to address this in it's current state? On Scala, even when providing an `ExecutionContext` where `prepare` will copy the MDC across. I have seen that MDC...
I think the behaviour should be configured through sim implementation. Though a more reproducible behaviour should probably be the default.
I think so far we only use defaults for codex definitions, not sim behaviour. My preference would be to encourage sim implementations when out-of-the-box behaviour is not enough (meaning we...
This is minimally supported by [protean/core/generation/json.clj](https://github.com/passivsystems/protean/blob/develop/src/protean/core/generation/json.clj). We might want to think about putting it in a separate project and maturing there.
Interesting use of extending the json schema with "faker" data generation: http://json-schema-faker.js.org/#gist/5f81f118fbd4eac01ccacf23a061a8b9 We could similarly refer to the codex from json schema. E.g. reference the codex type for property generation.
Is the purpose for sim behaviour? In which case, sim lib may handle it?