You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if the "outputs" for a cell contain a change, nbdime shows the entire list of outputs for both, even if the change is small and the full list of outputs large. This can result in large areas of unchanged text. See the screenshot below, which shows a simplified example containing eight output items preceding a deleted output item (though imagine this being 100 hundred items).
It would be better if nbdime used e.g. Git's approach of showing a limited and/or configurable amount of context. For example, git-diff has the --unified=<n> option, which "Generate[s] diffs with lines of context instead of the usual three."
In nbdime's case, it could for starters use individual items in the "outputs" list as a stand-in for lines (as the "outputs" key-value is a list of output items), as opposed to individual lines within each output item. (The latter could be a more advanced approach considered later.)
In this example, the json looks like this (excerpt):
Currently, if the "outputs" for a cell contain a change, nbdime shows the entire list of outputs for both, even if the change is small and the full list of outputs large. This can result in large areas of unchanged text. See the screenshot below, which shows a simplified example containing eight output items preceding a deleted output item (though imagine this being 100 hundred items).
It would be better if nbdime used e.g. Git's approach of showing a limited and/or configurable amount of context. For example,
git-diff
has the--unified=<n>
option, which "Generate[s] diffs with lines of context instead of the usual three."In nbdime's case, it could for starters use individual items in the "outputs" list as a stand-in for lines (as the "outputs" key-value is a list of output items), as opposed to individual lines within each output item. (The latter could be a more advanced approach considered later.)
In this example, the json looks like this (excerpt):
The text was updated successfully, but these errors were encountered: