Mya

In v1beta, I've noticed this far less often. I suspect it's due to the improved data model.

Another option could be to use something like otto: https://github.com/robertkrimen/otto This would let us replace the core of the extractor process with go and have some basic javascript evaluation capabilities.

someone suggested having the swagger explorer as part of the root

The URL used to be / is used to infer a module name. I didn't persist this model in the v1beta model: https://github.com/depscloud/api/pull/70/files#diff-2d509e895e6903a5a290a5f41c6fba49R50-R53

You could pull the url from a `.git/config` file.

The extraction logic is a gRPC service so calling it from Go should be doable. Most of the logic is already implemented in the indexer process. Here's the related block...

This should be stored on the edge between the source and module.

This will require an associated depscloud/api change

@PankhudiB no. The extractor process matches files based on a set of patterns. In this [commit](https://github.com/depscloud/depscloud/commit/d84e2b98433cc8e09bae232deffa7cbfe417b429) I went through and added `testdata` as an ignore for every extractor. This can...

This should use the SearchService to perform the traversals.