actions.yaml and config.yaml are inconsistent about integer types
Bug #1992173 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
actions.yaml and config.yaml don't agree whether it should be called "int" or "integer". (one requires one spelling, the other requires the other spelling.)
It would be good for new versions of Juju to allow both, and possibly to warn that it will be incompatible with older versions. But we definitely want to move towards a consistent spelling between both of them. (since we use 'string' I would also use 'integer' as the preferred spelling).
If we choose to support both spellings for the side that currently uses 'int', I think we could do this in a 2.9 release.
Changed in juju: | |
milestone: | 2.9-next → 3.2-beta1 |
Changed in juju: | |
milestone: | 3.2-beta1 → 3.2-rc1 |
Changed in juju: | |
milestone: | 3.2-rc1 → 3.2.0 |
Changed in juju: | |
milestone: | 3.2.0 → 3.2.1 |
Changed in juju: | |
milestone: | 3.2.1 → 3.2.2 |
Changed in juju: | |
milestone: | 3.2.2 → 3.2.3 |
Changed in juju: | |
milestone: | 3.2.3 → 3.2.4 |
Changed in juju: | |
milestone: | 3.2.4 → 3.2.5 |
tags: | added: charm |
Changed in juju: | |
milestone: | 3.2.5 → none |
To post a comment you must log in.