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

Allow looking up component code from trace #6

Open
jonnor opened this issue Nov 22, 2015 · 0 comments
Open

Allow looking up component code from trace #6

jonnor opened this issue Nov 22, 2015 · 0 comments
Labels
Milestone

Comments

@jonnor
Copy link
Collaborator

jonnor commented Nov 22, 2015

Would require the trace to either:

  • Have code of all components included (very large, and won't work for non-component things included by component)
  • Have enough info to know which component versions where, and how to look up the info. For node.js, this could based on a npm list dump, though maybe one should extract repo (typically but not alway github) from the package.json right away. Then would have to get the path from base of repo to the particular component. And have a way to HTTP GET the actual source code..

Since we want this in a non-NPM specific manner in general, there are some relationships here to noflo/noflo#247

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant