| Summary: | Account: [impl needed] add CreateWithProperties or equivalent | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Simon McVittie <smcv> |
| Component: | tp-spec | Assignee: | Simon McVittie <smcv> |
| Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| URL: | http://git.collabora.co.uk/?p=user/smcv/telepathy-spec-smcv.git;a=shortlog;h=refs/heads/account-creation | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | 21170, 21171 | ||
| Bug Blocks: | |||
|
Description
Simon McVittie
2009-01-06 11:42:28 UTC
Incomplete spec wording: http://git.collabora.co.uk/?p=user/smcv/telepathy-spec-smcv.git;a=shortlog;h=refs/heads/account-creation Unresolved: * how does the caller tell which properties this AM will accept "at construct time"? * what happens if the caller gets a property value wrong? As currently implemented in MC, it's silently ignored * what happens if the caller passes an unsupported property name? Sortable summary Resolution of three fixmes: * SupportedAccountProperties property * NotImplemented if name is unknown to the AM * InvalidArgument if value or type is nonsensical * (bonus fixme) MC should actually do this, and actually be atomic Fixed in 0.17.24 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.