Error at getting repositorys
See original GitHub issueLooks like the path issue is fixed.
but now it throws an error at the dependecies option:
uncaught at reactByUpdatingFoldersState TypeError: Cannot read property ‘dependencies’ of undefined
on Tree.js
{dependenciesDiagramOn && selectedNode.dependencies && ( <DependenciesTree namespace={namespace}
_Originally posted by @Motytheultimate in https://github.com/Bogdan-Lyashenko/codecrumbs/issues/14#issuecomment-463325932_
Issue Analytics
- State:
- Created 5 years ago
- Comments:18 (10 by maintainers)
Top Results From Across the Web
Troubleshooting cloning errors - GitHub Docs
If you're having trouble cloning a repository, check these common errors.
Read more >Repository management shows error "Could not get ...
The repository management in Bitbucket Datacenter shows error "Could not get repositories" as shown in the below screenshot.
Read more >Git error - Fatal: Not a git repository and how to fix it | Datree.io
This error means you attempted to run a Git command, but weren't inside a Git repository. Make sure you've: Navigated to the right...
Read more >Solving “Fatal: Not A Git Repository” (Or Any Of The Parent ...
In this article, we will explore what causes, how to prevent, and how to solve the “fatal: not a git repository” error.
Read more >Fix Git's 'fatal: repository not found' error quickly | TheServerSide
Fix Git's repository not found error · 1. You did not authenticate · 2. Your password has changed · 3. You are not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hm, interesting… yeah, makes sense, but still quite inconvenient) will see if I can fix it easily to resolve to correct file even when it starts from ./ Thanks 😃
@Motytheultimate yep, that was related to path separator as well, fixed in v 1.0.23 🙂