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

Systematic but simple way to enforce coherence and chainability between components #142

Open
hunterhector opened this issue Jan 30, 2020 · 0 comments
Labels
enhancement New feature or request priority: low Low priority, can be addressed later topic: infra Core infrastructure related issues.

Comments

@hunterhector
Copy link
Member

We have previously designed the "input_info" and "output_info" system to help enforce the constraint between the components. But it creates many extra boilerplates for people to implement, what's worse is these simple requirement check may not handle complex cases. But we still face problems at times, for example, if a prior system did not produce the annotation, or both systems are producing the same annotation.

We need to propose systematic method to handle such cases, but without introducing a lot of troubles to users. We also need to consider the problem from both static check and run-time check.

@hunterhector hunterhector added enhancement New feature or request priority: low Low priority, can be addressed later topic: infra Core infrastructure related issues. labels Jul 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority: low Low priority, can be addressed later topic: infra Core infrastructure related issues.
Projects
None yet
Development

No branches or pull requests

1 participant