avo-hq/avo

Key Value schema

Open

#3,884 opened on May 26, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Ruby (1,778 stars) (308 forks)user submission
EnhancementFieldHelp wantedStale exempt

Description

Feature

It would be nice to have some kind of schema or guidance for the key value. For example, if the record is a request and the field is field :headers, as: :key_value, it would be nice to specify that a few common keys might be Content-Type and maybe (second iteration) the value is application/json.

A few thoughts. The schema should probably be optional, meaning that when you save the record, it shouldn't be applied automatically. So for our example, if the user doesn't fill it in, the field value should not be {"Content-Type": ""}, so it should be suggested in the UI.

Current workarounds

Add a help option or maybe a default (but that would be a bit intrusive).

Contributor guide

Key Value schema · avo-hq/avo#3884 | Good First Issue