Key Value schema · avo-hq/avo#3884

(0 评论) (0 反应) (0 负责人)Ruby (1,778 star) (308 fork)user submission

EnhancementFieldHelp wantedStale exempt

描述

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).

贡献者指南

技术栈: rubyrails
领域: backendfull stack
议题类型: feature
难度: 3
预计时间: 1-2 days
活动状态: fresh
清晰度: mostly clear
前置要求: Familiarity with Avo field typesRuby on RailsBasic understanding of key value data
新手友好度: 35
研究方向: Investigate the current key value field implementation in Avo, likely in app/fields or lib/avo/fields. Review how other fields implement schemas or validation. Propose an optional schema that suggests common keys like 'Content Type' in the UI, without enforcing upon save. Consider adding a 'help' or 'default' option as a workaround, but aim for a dedicated schema attribute. Check for any existing discussions or PRs related to field schemas.