forked from tywalch/electrodb
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Feature/complex types for real (tywalch#73)
* Working tests but complex types still need to be modified for `required`, `hidden`, and `readOnly` * Updates work I think * Update progress * update progress!!! * put improvements * Seemingly making progress but I gotta be honest: I'm not really sure I am... * Adding additional type types * Removing Defaulted because it was not accurate here * Improvements to match new `set` definition style * Attribute improvements to include only relevant fields. No nested enums. * Overall improvements, before splitting Attribute into more specialized attributes, adding some typing refactors * get/set return type improvements! * Example and type improvements * Working tests, broken out Attribute classes * Type improvements! * Working set! * Consistency to getter/setters * type tests for type changes: required properties should not be able to be removed via remove method * Further test improvements for complex attributes * Type and test improvements * I have to figure out how to apply required/not required constraints to nested maps through the update chain methods * Cleanup * Defaults before required * Using the client's createSet functionality if provided * createSet without a client test * README and type improvements * Test improvements * value operation bug fixes * Implementation of Issue#71 * Complex attribute validation improvements * Cleanup * README Cleanup * Type improvements for GET, readme improvements, new type tests for GET * Example improvements * Package bump, readme improvements * Fixing typing issues with adding `null` as a possible response type from the `get` method * Adding changes to CHANGELOG.md
- Loading branch information
Showing
29 changed files
with
6,088 additions
and
735 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.