acalejos
I’m excited to share Merquery, a new library I’m working on to bring interactive HTTP tooling to Elixir.
This project started off as a way to practice making Livebook Smart Cells, where I wanted to implement a Postman-Styled Smart Cell. As I made progress I realized that there’s a lot of potential in this tool for tighter integration with Elixir.
Merquery currently consists of 2 components:
MerquerySmart Cell that provides an interactive way to work with HTTP requests, akin to Postman- A
mixtask –mix merquery.generate– which introspects on your router and generatesMerquerysmart cells pre-filled with the information relevant to each route.
Merquery takes advantage of the Livebook ecosystem to have built in support for serialization and secret storage, so you can save queries for later usage and use keys from your Livebook Hub token vault.
It also can be used to generate source code just as all Smart Cells do. You can use Merquery as a learning tool to learn how to use Elixir HTTP clients.
The library is currently in its infancy, but below are some ideas I have going forward.
These are just some ideas for features I currently have, but are subject to change:
- Finish basic REST operations support
- Registering custom plugins
- Improve
mix merquery.generate- Allow customized parameters for routes, etc.
- Add Table of Contents at Top
- Migrate to TailwindCSS and distinctive design palette
- Req plugin discoverability - Host a location where Req plugins can be submitted for others to
discover for use withMerquery - Livebook routes instant deploy - Have a mix task (e.g.
mix merquery.deploy) to automatically
deploy the generated livebook frommix merquery.generate - Support other HTTP clients and their unique features (HTTPoison, Tesla, etc. )
- Move Vue to Composition API and breakout components to SPCs
Any feedback is much appreciated!
Where Next?
Trending in Announcing
Other Trending Topics
Latest Phoenix Threads
Latest Livebook Threads
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 7 of 7 Posts
jonatanklosko
@acalejos cool stuff!
FTR we’ve recently started using an actual bundler setup in Kino and moved towards React for smart cells, with Tailwind. There is a
@livebook/kino-bundlerpackage that encapsulates the basic setup (including Livebook Tailwind config). You can seekinoRemote execution cell orkino_bumblebeeTask cell for examples. Still, the idea is that you can use whatever setup and framework you prefer, I am mentioning this just for completeness : )krasenyp
Please, don’t say CRUD/REST. They’re not equivalent. Quite the opposite, actually.
linusdm
Awesome! A programmable postman. Very cool.
Having a mix task to side-load Livebook in any mix project would be useful. Maybe that could be solved generically, and not specifically for Merquery. I have projects that have some livemd files useful during development. Although Livebook desktop is super easy to set up, it would be even smoother to have a mix taks you could fire up, with a specific livebook loaded by default. Just thinking out loud here…
acalejos
@krasenyp
Good point, not sure why I put CRUD. Probably typing too fast. Removed mention of it in the post
@jonatanklosko
Thanks for the suggestion and all of the great work on Livebook! I already wanted to move to Tailwind and clean up the JS side, so I think that would be a good move. Looking at the repos you mentioned, it seems much cleaner.
@linusdm
Yeah that sounds like a more generic use case. Perhaps it would involve starting up a Remote Execution Cell
Glad you like it! Yeah, I think Req plugins offer an easy entry point for customizing it, and plan on leaning into them with this project.
acalejos
I’ve added some more features to this as well as fixed several bugs. Currently still just on GitHub Main
Highlights:
Demos:
https://x.com/ac_alejos/status/1798180009300926797
https://x.com/ac_alejos/status/1798199529285779929
https://x.com/ac_alejos/status/1798920380704510460
acalejos
Big update added support for request bodies, the last major missing component.
Demos:
https://x.com/ac_alejos/status/1801811605123928566
https://x.com/ac_alejos/status/1801819740370878739
acalejos
Added support for passthrough options and made a new, more comprehensive demo showcasing many of the newer features:
GitHub API Demo