ckan / ckan/ckanext-scheming

Empty selectable field problem

Open
#56 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
102
Forks
182
PR merge metrics
No merged PRs in 30d

Description

Hi again,

I have been customizing a schema and I'm doing some tests. It seems that is working quite very well but I am having problems for a Selectable field: If there is no choice selected from a selectable field then the following value appears in the field (once I've created a new dataset).

> Project-Id-Version: CKAN Report-Msgid-Bugs-To: EMAIL@ADDRESS POT-Creation-Date: 2015-01-26 11:55+0000 PO-Revision-Date: 2015-02-25 10:36+0000 Last-Translator: Adrià Mercader adria.mercader@okfn.org Language-Team: Catalan (http://www.transifex.com/projects/p/ckan/language/ca/) Plural-Forms: nplurals=2; plural=(n != 1) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Generated-By: Babel 0.9.6

My dataset configuration is below:

> ```
> {
> "field_name": "city_integration",
> "label": "Integration",
> "help_text": "Is integrated in City DB?",
> "help_inline": true,
> "preset": "select",
> "choices": [
> {
> "value": "yes",
> "label": "Yes"
> },
> {
> "value": "no",
> "label": "No"
> }
> ]
> }
> ```

And preset configuration is below:

> ```
> {
> "preset_name": "select",
> "values": {
> "form_snippet": "select.html",
> "display_snippet": "select.html",
> "validators": "scheming_required scheming_choices"
> }
> }
> ```

What I've made it wrong? May do I should to change the "validators" specified on the preset?

I would appreciate any advice.

Thanks.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the select preset configuration and its select.html form and display snippets, then reproduce the dataset-creation flow with no choice selected. Check whether the validators or the select rendering produces the displayed translation metadata. Done means an empty selectable field remains blank when a new dataset is created.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.