What is navigability?
I made up this word in the same manner as read-ability. If readability βis the ease with which a reader can unders...
For further actions, you may consider blocking this person and/or reporting abuse
The word already exists - Navigability
Yes, I saw this word. But according to oxford dictionary navigability - βthe degree to which a river, lake, etc. is wide enough for ships and boats to sail on. I wasn't sure if I can reuse it here
Yes, in that usage, it is the degree to which a river etc. can be navigated - i.e. how easy it is for the ships captain to navigate their way through. It's exactly the word you need - but you're using it in the sense of how easy some code is to navigate by someone who is reading it
My favourite solution is to have component based folders if possible.
Foo/
Foo.js
Foo.scss
Foo.test.js
I've worked on codebases where file "type" organisation is used. It's also fine, but since related files are scattered in multiple places it just takes a bit longer to find them, create them, and also make sure you've done all necessary changes each time.
For searching, I just use the IDE to search by filename.
+1
We also recently started putting all files in one folder, especially JS and CSS files. We started off with a different folder for all of the CSS. Finding the right CSS file is particulartly tedious.
There is the bookmark functionality in most editors, where you can keep important positions in files. I do this while working on a certain feature and remove them when Iβm done. I like to have long files rather than lots of files, and this makes jumping around easier.
I prefer more files over longer files. Its easier to merge. The syntax colorizer and other editor tools (and partial builds) are faster. And its faster to reason about as a whole.
But cant avoid the large files, so one thing ive always wanted in editors are the ability to drag a single block of code into its own virtual editor. A kinda focus mode. No accidentally scrolling away. And a search that only find text within that block of code.
Emacs narrowing welcomes you.
This seems like tool issue. There are editors which can be really fast (something native instead of electron based). There are projects like tree sitter which can help here.
Bigger number of file require context switch when jumping between files while reading files.
Nice idea)
I didn't even thing about the colorizer since I'm using a B/W color-scheme. But yes, usually it's not a problem even with VSCode. Only when opening compiled/minified files by accident.
Indeed bookmarks is one more navigation pattern known since printed media
I'd love to see data flow or call graph visualization showing the composition of an endpoint in one swoop.
Haskell has Hoogle which finds functions by signatures.