avo-hq/avo

Key Value schema

Offen

#3.884 geöffnet am 26.05.2025

 (0 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Ruby (308 Forks)user submission
EnhancementFieldHelp wantedStale exempt

Repository-Metriken

Stars
 (1.778 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 1T 6h) (67 gemergte PRs in 30 T)

Beschreibung

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