Description

Description:

You may not need to document this change independently from the rest of the field-level encryption project, but I'm not totally sure. This change made it possible to use the JSON Schema 'additionalProperties' keyword to indicate that all other not-explicitly-named properties are encrypted. For example, consider the schema {type: "object", properties: {foo:

Unknown macro: {type}

, bar:

Unknown macro: {type}

, additionalProperties: {encrypt: {}}}. This schema means that field "foo" must be a string (if it exists), field "bar" must be a number (if it exists), and all other fields must be encrypted.

Engineering Ticket Description:

The result of parsing additionalProperties should be an edge in the encryption tree which represents the "else" case, meaning take this path if no other edges match the current path component. This ticket should include the schema parsing as well as the tree traversal.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)