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

Data enrichment #253

Open
mjpitz opened this issue Mar 19, 2021 · 0 comments
Open

Data enrichment #253

mjpitz opened this issue Mar 19, 2021 · 0 comments
Labels
effort: 8 type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: complicated The situation is complicated, good practices used.

Comments

@mjpitz
Copy link
Member

mjpitz commented Mar 19, 2021

This will be a rather arduous task, but there's a lot of room for improvement on the extraction side of the world. For example, some languages support pulling in additional files. requirements.txt is one where it can load context from other requirements.txt files. Similarly, pom.xml can reference variables defined within properties files, build.gradle pairs with settings.gradle, and so on. And yet, we don't know the contents of these files until after they've been matched and the contents have been extracted.

We should find a way to support this pattern as it's somewhat common enough to pose some head aches.

@mjpitz mjpitz added effort: 8 type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: complicated The situation is complicated, good practices used. labels Mar 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: 8 type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: complicated The situation is complicated, good practices used.
Projects
None yet
Development

No branches or pull requests

1 participant