Skip to content

Conversation

@Merlijn-D
Copy link

Adds persistence to the analysis state

Fixes #13

These encoders automatically open the array/map for you.

They also add a function to `Writer` that allows you to write one or two
values, these values wile be written differently based on what encoder
you use.
… function

You no longer need to overwrite the extension methods, but can override
the normal functions that are used by the extension methods.
This is to avoid ambiguity when importing form multiply places
Only noEnvironment is currently implemented
`-s` is used to select the file you want to save your analysis to
`-l` is used to select the file you want to load your analysis from
Encoders for super-types (e.g. Address) need to distinguish their sub-types, then
encoding of these sub-types was sometimes done inside of the encoder of
the super-type. This is now changed.
JSON keys can only be strings, so you should not be able to use any
other type as key.
If you are using ArrayKeyEncoder, you can use different types, because
keys are stored as normal array elements, and not as keys.
The `Int`, `Boolean` and `String` were using `toString`, they are now
correctly encoded.
This allows you to save the ID of components without specifying what
kind of component you want to save.
Change name of parent folder for persistence code from `save` to
`persistence` to increase clarity.
This allows for the non-inclusion of optional values inside of maps
This allows for the non-inclusion of optional values inside of maps
I was encoding the global worklist instead of the worklist that was
given to the encoder
Instead of creating a new type `WorklistComponent`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Persisting the analysis state

1 participant