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

highlevel: guarantee that elektraGet succeeds #2765

Open
markus2330 opened this issue Jun 9, 2019 · 2 comments

Comments

2 participants
@markus2330
Copy link
Contributor

commented Jun 9, 2019

As written in #2382 we want to guarantee that elektraGet always succeeds.

There are different point of times when type checking can take place:

  1. during kdbSet: Of course it is always better to never make configuration mistakes persistent. But Elektra cannot guarantee that in some way or another the type checking is circumvented.
  2. during elektraOpen: here we can guarantee that type checking is not circumvented by:
    • use built-in spec if no spec is provided
    • fail if type plugin is not available
    • fail if the type plugin reports warnings/errors
@kodebach

This comment has been minimized.

Copy link
Contributor

commented Jun 9, 2019

Before we can discuss this issue we need to clarify one thing: Are we talking about the highlevel API by itself or are we talking about the highlevel API in combination with code-generation? The ideal and also the possible solutions are very different for the two cases...

@markus2330

This comment has been minimized.

Copy link
Contributor Author

commented Jun 9, 2019

Actually, the guarantees should be nearly the same except that the one without code generation fails if spec is missing (and, of course, cannot provide type safety).

If there are further differences: let us concentrate on the one with code generation as it is the recommended way to use the highlevel API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.