Age | Commit message (Collapse) | Author |
|
still need to bind signals properly, and block on the validation
process until we receive the "connected" signal. but the basic flow
is working again, i.e, user should be able to remove the .config/leap
folder and get all the needed info from the provider.
|
|
and changes to functions having to do with the default
path to certs.
|
|
and type casting.
|
|
and a jsonvalidate function too,
that calls to jsonchemea.validate(self, data) with self.schema
We're using the specs to both purposes now:
* providing a type casting system for our config options (work in
progress for the type casting)
* json schema validation
|
|
|
|
|
|
now callables are allowed in specs *only at one level depth*
to allow for last-minute evaluation on context-sensitive data,
like paths affected by os.environ
also some minor modifications to make check tests pass after
putting the new jsonconfig-based eipconfig in place.
aaaaaall green again :)
|
|
|