streamparse

streamparse copied to clipboard

In #158, this came up and is its own issue:

This raises questions about streamparse's config.json loading. It's a lazily loaded config, where values are pulled as needed via get_env_config in the source. We could consider a configuration object which loads all configuration early and validates it, also pointing out unknown keywords which were provided. This approach would give clear feedback to the user as to whether config.json is valid. #11 discusses whether to use Storm YAML configuration.

I considered adding configuration directives via Storm configuration options for birding but preferred (a) hierarchical definitions (maybe Storm YAML supports this) and (b) a validation step. The resulting implementation may be relevant to this issue.