Skip to content
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

On-demand loading of meta info #176

Open
tecimovic opened this issue Jun 21, 2021 · 0 comments
Open

On-demand loading of meta info #176

tecimovic opened this issue Jun 21, 2021 · 0 comments

Comments

@tecimovic
Copy link
Collaborator

Zap is currently doing the following wrong thing:
1.) When starting up, you specify the ZCL and generation meta-info files.
2.) Zap will physically load those two bits of data into the database upon startup.
3.) When we load the .zap file, it will attach to these.

This model completely breaks-down when we load in the multiple .zap files that are based on different SDK.

The required flow is the following:
1.) We specify ZCL and generation meta-file at startup but those are just DEFAULT values.
2.) We do NOT load them at startup.
3.) When we open a "new configuration", we only then load in the DEFAULT metafiles, unless previously loaded.
4.) When we are loading in a .zap file, we take the values of the meta-file from the .zap files and:
a.) we load them in at this point, if not yet loaded.
b.) if we can't load them, we ask the user if it's ok to use DEFAULTS.
c.) user may also choose to point to a whole-different set of files which we load in at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant