Biiiiiiig merge more than use new iden3js version --> SO SORRY CREW!!!! :/
Apply SOLID patterns.
Separation of concerns.
Clearer architecture (I guess).
Get rid of logic in the views and dependencies in order to can reuse all the other logic (app state, API, helpers, etc..) if we move to React Native.
Apply module patterns to don't pollute too much global scope and only try to use Classes if we need a Singleton (further than the views and components that we use Classes always).
Add comments.
Try to use Immutable in almost all the app state.
Created an own SCHEMA VALIDATION module to parse responses and to have the same in the storage and in the app state. By now only for the identity entity. Need to create for the claim.
Changes in webpack for production mode.
Changes in Eslint.
Some small performances issues.
Biiiiiiig merge more than use new iden3js version --> SO SORRY CREW!!!! :/ Apply SOLID patterns. Separation of concerns. Clearer architecture (I guess). Get rid of logic in the views and dependencies in order to can reuse all the other logic (app state, API, helpers, etc..) if we move to React Native. Apply module patterns to don't pollute too much global scope and only try to use Classes if we need a Singleton (further than the views and components that we use Classes always). Add comments. Try to use Immutable in almost all the app state. Created an own SCHEMA VALIDATION module to parse responses and to have the same in the storage and in the app state. By now only for the identity entity. Need to create for the claim. Changes in webpack for production mode. Changes in Eslint. Some small performances issues.