Open helloanoop opened 6 months ago
I feel that TOML should be the way forward. Would appreciate more articles on TOML vs bru as you move forward with the next steps.
any update on this ? this seems very interseting
Hey @helloanoop, just wanted to know did you also explore/consider YAML for the language?
Hey @helloanoop, just wanted to know did you also explore/consider YAML for the language?
My bad, went through #360 , indentation hell 🤔 interesting, I mean at one point it can become that but then at that point your API design is not good, It will be on the type of API imo.
I think TOML is a better format for humans. It's too easy to mess things up in YAML.
Overview
This discussion aims to explore the possibility of using
.toml
as the preferred format for saving API request data instead of.bru
. For the progression of the Domain-Specific Language (DSL), see https://github.com/usebruno/bruno/discussions/360I've been seriously exploring how we can represent api requests in
toml
After careful consideration, factoring in various edge cases,toml
seems to fulfil our requirements and might offer better long-term benefits.Why TOML
Tasks
More Tasks TBD based on how the experiment turns out
Looming Issues
Several features are currently blocked due to limitations in the bru language. Some include:
To address these limitations, I see two potential paths:
Next Steps
Before choosing a direction, I aim to implement experimental TOML support in our current app within the next 3-4 days (by January 1st, 2024). . BTW I am working on bruno Full Time from Jan 1st :)
Sample GET Request