Underlying values of selects should allow hyphens/dashes because it's human-friendly a

Should just be part of <a class="issue-link js-issue-link" data-error-text="Failed to

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

hey <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url=

Underlying values of selects should allow hyphens/dashes and be constrained to 32 chars about build HOT 8 CLOSED

getodk commented on August 23, 2024

Underlying values of selects should allow hyphens/dashes and be constrained to 32 chars

from build.

Comments (8)

issa-tseng commented on August 23, 2024 1

Should just be part of #46, no?

from build.

florianm commented on August 23, 2024 1

Thanks @clint-tseng, this will make my data ingestion much easier, as it allows field names to match exactly.

from build.

florianm commented on August 23, 2024 1

@clint-tseng thanks heaps!

from build.

florianm commented on August 23, 2024

+1 for dashes!

from build.

issa-tseng commented on August 23, 2024

How about periods? Those are valid per XML spec.

from build.

yanokwa commented on August 23, 2024

Good question. I've tested a small sample form with periods in column names and in calculations it works in an end-to-end test using XLSForm and Collect and Aggregate.

I think we should add period support to control and group names as well. @clint-tseng, can you file that as a separate issue?

from build.

florianm commented on August 23, 2024

@lognaturel @clint-tseng apologies for the poke - is this feature live yet at build.opendatakit.org (showing version 0.90)?
On http://staging.build.opendatakit.org/ (also showing version 0.90) I can see that this feature works already.

from build.

issa-tseng commented on August 23, 2024

hey @florianm: sorry about the delay; it should be working now.

from build.

Recommend Projects