-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RELEASE 2.0.0] #44
Draft
mtmr0x
wants to merge
27
commits into
main
Choose a base branch
from
v2.0.0
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
[RELEASE 2.0.0] #44
Conversation
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
mtmr0x
added
feature
New feature (in Roadmap)
documentation
Improving or fixing documentation
labels
Dec 10, 2020
- change contractVerification name to transactionVerification; - remove responsibility of saving from indexSearch - put responsibility of saving in save function - remove update type - reorganise type declarations for update return
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes summary
update
works for empty states (when they are just created);dispatch
function;eslint
today;Changelog
1. simplify documentation for better understanding with simpler examples
2. improve how
update
works for empty states (when they are just created)The
update
algorithm received some design improvements, but the main change that made it possible to update data never dispatched was creating the store with its keys in null or empty values.3. aim for removing or create a deprecation process for
dispatch
functionThe
dispatch
function will be entirely removed of use. The new API for Nucleo does not fit this method anymore and anupdate
like method will be used for all kinds of updates to the store.4. logo (finally)
5. improvements in type declarations for several areas pointed by the project
Eslint
todayfields
are verified as well.6. Change API usage to a more modern approach (breaking change)
Mostly, working on that. Here's a preview:
7. Lists of Objects being able to be created without all fields, setting the missing ones as null
8. Study the ability to push to Lists
TL;DR; not possible right now.
I would have to create a query API like MongoDB and it would add substantial extra work on this. I'm studying the possibility of Nucleo State receive atomic items and lists as well, not only "Objects" HashMaps, like: