Background: I have a pull request into a repository where the npm module isn't up-to-date with master, and I'd like to test out my branch in a module that depends on it through a bunch of different deep dependencies. It seems like patch-package would be a great solution for this.

Problem: When I append .patch to my GitHub URL it gives me a patch, but when I pass it to patch -p1 it

The current example in https://github.com/benjamine/jsondiffpatch/blob/master/docs/formatters.md does not trigger html arrows display.

This is the closest I've came up with to make it work :

  var delta = jsondiffpatch.diff(left, right);
  // left is optional, if specified unchanged values will be visible too

  var el = document.getElementById('the-diff');

 el.innerHTML = jso

Describe the Bug
Right-click options are gone when "Copy Selector" is enabled.

To Reproduce
Turn on "Developer Mode" and "Copy Selector", and right-click an image popup.

Expected Behavior
Options to copy/save image previews, copy/open links, in addition to Copy Selector.

Screenshots

![image](https://user-images.githubusercontent.com/26673668/80513012-68621680-894c-11

New to Go. Would like to use this library, but don't see any examples or documentation. Even the most minimal documentation would be useful to new Go developers like myself.

We started using the library and on a specific scenario, we have to use Ecto.Multi .
Looking through the documentation/code, the usage of ExAudit.Tracking.track_change implies that user will build the resulting_struct through Ecto.Repo.Schema and that is clear unless you go through the codebase.
Also, Ecto Documentation does not expose Ecto.Repo.Schema which makes the usage trickier.

We need documentation for our code.
I propose following the google styleguide:
https://google.github.io/styleguide/cppguide.html

specially just go to how to comment functions. Most functions are NOT SELFEXPLANATORY. And i spent now hours over hours to find out what just single functions do. Let alone a set of functions, called in a specific order. This must stop.

The bare minimum for me wo

To remove the buggy programs used in tests, located in examples folder, we can create another repo and put all of them there.
Then, we include an script that clone the repo, triggers the buggy programs' compilation, etc