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

improve config parsing to accommodate type casting and validation rules #130

Open
msramalho opened this issue Feb 14, 2024 · 1 comment
Open
Labels
enhancement New feature or request nice to have Issues that are not a priority but would enrich the project.

Comments

@msramalho
Copy link
Contributor

As it stands the logic to handle the configs() method of each Step (like Archivers, Enrichers, ...) does not cast int/float/bool and uses only strings. Likewise it's proven quite useful to specify validation rules in the configs rather than relying on the init method of each Step to do so.

This issue is on adding both of those configuration parsing mechanisms and refactoring existing Steps that are doing internal casting/validation.

@msramalho msramalho added the enhancement New feature or request label Feb 14, 2024
@msramalho msramalho assigned msramalho and unassigned msramalho Apr 9, 2024
@msramalho msramalho added the nice to have Issues that are not a priority but would enrich the project. label Apr 16, 2024
@msramalho
Copy link
Contributor Author

this still remains a good coding challenge that would make developing new features smoother.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request nice to have Issues that are not a priority but would enrich the project.
Projects
None yet
Development

No branches or pull requests

1 participant