[MONGOCRYPT-56] make status-handling consistent across types Created: 13/Mar/19 Updated: 28/Oct/23 Resolved: 15/Mar/19 |
|
| Status: | Closed |
| Project: | Libmongocrypt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Samantha Ritter (Inactive) | Assignee: | Samantha Ritter (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Build libmongocrypt library |
| Description |
|
Some types (encryptor, decryptor) hold their own status objects inside them, and on failure, the caller checks the status with a mongocrypt_type_status method. Other types (key_broker) require a status to be passed into each function call. Let's pick one of these conventions and use it for all our public API. |
| Comments |
| Comment by Githook User [ 15/Mar/19 ] |
|
Author: {'email': 'samantha.ritter@10gen.com', 'name': 'samantharitter', 'username': 'samantharitter'}Message: |