Named operations bypass any normalization done by fields
Bug #400477 reported by
Curtis Hovey
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
| lazr.restful |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When calling named operations on the web service, the IField API is only used to validate the parameter.
The IField.set() method is never called (because there is no real context to which to assign the value). When IField do normalization in the set() method, that normalization won't happen on named operation parameters.
The fix would be to create a "parameters context object" which is bound to the field and call set() to set the parameters value. And then retrieve the value to use for the underlying method calls from this parameter object.
| Changed in lazr.restful: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in launchpad-foundations: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in lazr.restful: | |
| importance: | High → Low |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| summary: |
- FieldMarshallers do not honor a Field's set() rules + Named operations bypass any normalization done by fields |
| description: | updated |
| tags: | added: api |
Revision history for this message
| Francis J. Lacoste (flacoste) wrote | #2 |
| tags: | added: tech-debt |
Revision history for this message
| Robert Collins (lifeless) wrote | #3 |
| Changed in launchpad: | |
| importance: | High → Low |
To post a comment you must log in.
The create milestone form used the NoneableTextWidget to prevent meaningless code names from being created, but the field marshaller does not honour the rules, see bug 400268.