LocaleModel only represents language selection, not a full locale
Bug #1934114 reported by
Olivier Tilloy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| subiquity |
New
|
Undecided
|
Unassigned | ||
Bug Description
In subiquity/
""" Model representing locale selection
XXX Only represents *language* selection for now.
"""
This is confusing for clients of the REST API that need to know that the locale endpoint actually takes a language code as parameter for POST, not a locale.
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
To post a comment you must log in.
subiquity doesn't separate the language from location the way it should but it still expects en_GB.UTF-8 type strings to go to the locale endpoint. This isn't great and I would like to do something better eventually but it needs a bit of design work.