Father of AngularJS
Thanks! We even used angular! Though, mixed in with other things... It got kinda hectic.
Thanks for your comment!
It works by first looking for repos that have a package.json (which indicates that it's a nodejs project) and then parsing .js files on that project and render the final documentation.
This is just an MVP and needs lots of improvements on UI and also the final rendered output, but I'm glad I was able to show how it might work.
It is a system for developers to add scripting capability to their node.js apps.
Thank you! Participation in NKO for us just start and attempt to get some inspiration for future work. Unfortunately only 1 developer and PM in team at the moment, that's why UI sucks, anyway, we will continue that project and add more love in UI. At the moment we are working on deeper repository analyse, including comments, issues and activity in forks.
Hello! Thank you for stopping by to look at The Carlin Report. One of the goals in creating this app was to give an outlet for active transportation users to report these incidents. At least locally, as there is no "accident" these are not reported to police.
There could be a valid reason for these occurrences such as poor signage, road design, tall hedges, lack of bicycle lanes. Documenting these locations provides the ability for organizations to use them to back up claims when approaching municipal governments for changes to or requests for bike lanes.
We would hope that after the person has caught their breath and their bearings they would share the incident to make others aware. Community engagement is never a bad thing. Again, thank you for taking the time to look and comment.
These are great questions. So one aspect of our hack is we do in fact try to address magnification. Essentially our module detects if a file is minified (has a small amount of lines with a LOT of characters per line) and appends semi colons with new line characters. This way our diff can be on a line by line basis. In theory a minifier that is consistent would not produce noise in a diff between to files except around the LOC that actually changed.
I do not feel there are any more security concerns from this solution than traditional script serving models. The files themselves are stored in local storage, which inherits the same security as cookies and other locked down aspects under a domain. So scripts cannot be used from other domains.
@mhevery to provide a bit more clarity, here's what happens when a patch is applied with the dynoSrc client library via a call like this:
dynoSrc.apply("moduleName", "1.0.1", "git diff -- ... diff ...");
We did try to address minified files as @ryanstevens attested to. There is some debate about the merits of minification given how good gzip is on its own, and we wanted the tool to be agnostic to your decisions there.
That was the main design goal of the library: don't be opinionated, and offer a flexible library that can support various paradigms. You can use the server component to generate diffs that you apply w/ your own JS code, or you can write your own tool to send down diffs on a different stack than node and still use our client library to do the patch-ups and caching.