Skip to content

Simplify NP Config service consumption #36099

Closed

Description

Now the only way to get a config is to use atPath method, which requires ConfigClass creation.

ConfigClass: ConfigWithSchema<TSchema, TConfig>

That looks like an overhead for simple cases when Config is minimalistic
https://github.com/elastic/kibana/blob/75d01eed4007e7f3675b68c5b87edd1662dcd9d9/src/core/server/plugins/plugins_config.ts
We can add an alternative method that returns validated config and end users can map it to a ConfigClass if needed.

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

Metadata

Assignees

No one assigned

    Labels

    Feature:New PlatformTeam:CoreCore services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions