Scaffolding Script for Mac/iOS audio applications with HTML UI.
Catch-all repo for eagle libraries useful for EuroRack modular synthesizers
design files for cost-conscious DCO module for eurorack format modular synthesizers
A headphone amp/line amp output for Eurorack
Low cost open source Eurorack Mixer
audio unit plug-ins with rust and react-native.
buffered multiple for eurorack
html5 audio mucks your beats
pull request commentmorpheusgraphql/morpheus-graphql
I wasn't sure what the best tone for this would be, so I tried to write tutorial-style comments. Let me know if this makes sense, or if you think another format would be appropriate for the comments.
comment created time in 9 days
commit sha 7ec48d188726b1d6218b5ed567ab85b10209cedb
add tutorial-style running commentary
push time in 9 days
commit sha ee4d17dc80e33c7953e377abcac5a1c6e5b59ec1
push time in 12 days
commit sha a12fcb28b4d9869093d0d1504fa1900f68318b72
Feature/graphql client supports custom queries with json schema (#547) * init * queryType * validations * ParseType * String * Query * Client * mutation * testOperation * TestEnums * custom * update changelog * replace insert * const id * const id Co-authored-by: 7nalchev <email@example.com>
commit sha e59c17e205eb29ef1c480ccce085055a9fe5fbdb
Merge branch 'master' into example/fraxl
push time in 12 days
PR opened morpheusgraphql/morpheus-graphql
This is an example of using fraxl to batch database requests, which prevents the N+1 queries problem. Related to the conversation in #348
Probably a lot of room for improvement here - eagerly awaiting feedback/corrections
pr created time in 12 days
Haskell GraphQL Api, Client and Tools
fork in 12 days
Can do! Look for a PR sometime over the next week
comment created time in 14 days
Just wanted to chime in and say that I used fraxl, a clone of Haxl with more general types, to implement batching in my morpheus project. This worked really well for the purpose, and fulfills both requirements listed above (queries happen lazily, no N+1 problem).
To make it work, basically you define all your possible db queries in a GADT, then define a fetcher function that executes the queries. The fraxl library then calls the fetcher with groups of queries that can be batched together. fraxl uses the applicative
<*> to determine what group of queries can be batched together. For my (simple) program it seemed to give good results without much tweaking.
I'm not ready to share the whole project at the moment but I can go in to more detail on how this works if people are interested. It also supports optional caching which is a nice speed up if you happen to re-query anything.
comment created time in 15 days
commit sha dd8a747640df60dbe9d4d7f283bba70069e7eb0e
Update versions of dependent-map and dependent-sum This allows clients to use the convenient template haskell derive methods for the relevant classes.
push time in 15 days
PR opened ElvishJerricco/fraxl
This allows clients to use the convenient template haskell derive methods for the relevant classes.
pr created time in 15 days
started time in 16 days
started time in 17 days
started time in a month
started time in 3 months