Learn, design or document codebase by putting breadcrumbs in source code. Live updates, multi-language support and more.

Looks 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

Firefox displays this content when attempting to run codecrumbs against a simple, working react project.

Tested with 2 separate projects.

Corrupted Content Error

The site at http://localhost:2018/ has experienced a network protocol violation that cannot be repaired.

The page you are trying to view cannot be shown because an error in the data transmission was detected.

    Please contact the website owners to inform them of this problem.

I am not sure what additional information would be helpful. I also tried this in Opera. I am very interested in getting this working and any assistance will be appreciated.

I just started using codecrumbs, and I'm finding that the crumb code listings are not automatically scrolled to the crumb, they are scrolled to a vertical offset that is significantly smaller than the crumb offset, so that the crumb line is not visible unless I scroll it into view. :(

I peeked at the code, and the code for scrolling a crumb into view seems to hardcode a line height of 15. In practice, the line height is 18 (font size of 12px and line height of 1.5).

It seems that currently only one crumb per file is supported, however it would be incredibly useful if there was a way to do multiple crumbs.

The particular use case I am thinking of is a file (like a reducer) that might be involved in more than one trail.

PS Thanks for your work on this package, its a brilliant idea!

My Codecrumbs browser is in a perpetual loading state. I've added some logging on my end and it seems to be parsing the //cc comments properly, so I can't figure out why there is no visualisation.

Browser

Debug

hi there seems to be an error in your sidebar.js and a few more. i tried it with running your project directly from your sources.

the error i get is the follwing

uncaught at reactOnSourceSet TypeError: Cannot read property 'path' of undefined On example is at the follwing

  <React.Fragment>
  <div>{file.path}</div>
  <div className={'copyIcon'}>
    <Copy copyText={file.path} />
  </div>
</React.Fragment>

in sidebar js https://github.com/Bogdan-Lyashenko/codecrumbs/blob/master/src/public/js/components/sideBar/component/SideBar.js

I added php dependency support. (but php namespace-use only)

Also I changed behaver when checked for dependencies > direct only

Could you review it.

Feature change

• enabled full-featres support for php
• implemented parsing imported dependency and namespace dependency for php by php-parser
• added src-php in example project
• changed behaver of dependencies when checked for direct only

Whenever i save changes, codecrumbs still detect changes and recompile but the trail option on browser contain only current option, others are disappeared.

Hello, I'm playing with CC comments in my Go backend with lots of microservices, currently I'm trying to document a single flow of user authorization, that is split between different files. I'm using numbered code crumbs, but the view is getting skewed and not readable in the end, e.g.

I have multiple numbered CC's in the same file, so the view orders them not by the tailing order, but in the order of location in files. It think this is an issue, any suggestions how to avoid this?

Tried following the tips in issue #17 - but I still can not use the codecrumbs command. Also tried updating "ecstatic" but I get the same warning. Any ideas what's going on here?

Edit: Noticed there's a typo in my screenshot. Also using command codecrumbs -d src -e src/index.js was not effective

Hi,

This project looks really cool! Sorry if am being dumb or not looking for more info. But I can't seems to work this with my node-boilerplate. I added it as dependency and running it with this syntax.

$ npx codecrumbs -d src -e index.js

Environment

• Node/NPM - 10.7/6.1
• MACOS - Mojave(10.14.3)

internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module 'fs-readdir-recursive'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/home/t.kohler/.config/yarn/global/node_modules/codecrumbs/src/server/code-parse/language/php/namespaces.js:1:26)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)

Hi! Tried to launch the codecrumbs on the Python project and got this. May I ask for suggestions to fix this?

I struggle to make codecrumbs working for Typescript project I working on. Any suggestion what should I do to be able to use codecrumbs for a project?

Environment: Windows 10 with WSL2. codecrumbs installed in WSL2 OS.

How to reproduce:

• start codecrumbs in wsl console
• open browser and go to localhost:2018 (in Windows) After that client just hanging out. Console contains the message: "WebSocket connection to 'ws://127.0.0.1:3018/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED".

How to solve: It's need to just use localhost in url instead of 127.0.0.1. Otherwise ports from WSL are not accessible.

• [x] Added test:e2e script to package.json
• [x] Added page-objects dir to tests/e2e/ and created a page-model. (In Progress)
• [x] Added tests to cover some user-flows. (In Progress)

Finally go to trying this out last Friday and the navigation in vscode using -i code didnt work.

I notice today you have removed this '-i code' documenation in last few days.

This is no longer a feature?