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
It would be more consistent with other behavior if diff took the default diff output format from the file suffix.
The current behavior is a bit confusing, as the default "plain" is almost idiomatic markdown; for example, doing an arbitrary diff on 2 versions of envo with -o diff.md and no --format md gives lines like this:
If the diff consists only of deletions, then this looks like a markdown list, the <ENVO:01000197>[broadleaf forest biome] looks kind of like a broken markdown link.
This could be considered a breaking change which we don't do, in which case I think just an additional note of caution in the docs should be sufficient to close this (I can do this if this is the preferred action)
The text was updated successfully, but these errors were encountered:
It would be more consistent with other behavior if
diff
took the default diff output format from the file suffix.The current behavior is a bit confusing, as the default "plain" is almost idiomatic markdown; for example, doing an arbitrary diff on 2 versions of envo with
-o diff.md
and no--format md
gives lines like this:If the diff consists only of deletions, then this looks like a markdown list, the
<ENVO:01000197>[broadleaf forest biome]
looks kind of like a broken markdown link.This could be considered a breaking change which we don't do, in which case I think just an additional note of caution in the docs should be sufficient to close this (I can do this if this is the preferred action)
The text was updated successfully, but these errors were encountered: