[
https://issues.apache.org/jira/browse/NIFIREG-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313361#comment-16313361
]
Joseph Percivall commented on NIFIREG-77:
-----------------------------------------
Hey [~rmoran],
Totally agree with the need for a "diff" feature. I see the end goal of the
features and UX of versioned flows as very similar to the UX of git.
Thinking along the lines of git, the most used features in git are to see the
locally uncommitted changes and see what changed in the last X commits (i.e.,
checking a PR). That said, while they're similar, the mentality of each is
quite different and I don't think they should always be treated as such
(combining them into one "compare versions" action). The first is checking
things that have yet to be saved and can still be changed. The other is
verifying changes that have already been saved.
So I don't think having a shortcut for "show local changes" and the ability to
"compare versions" (including the local one) are mutually exclusive. I
understand wanting consistency, but I'm not convinced that changing "show local
changes" to only be a part of the "compare versions" would be a better UX.
> Allow a user to see the changes created by the currently loaded version
> -----------------------------------------------------------------------
>
> Key: NIFIREG-77
> URL: https://issues.apache.org/jira/browse/NIFIREG-77
> Project: NiFi Registry
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Joseph Percivall
> Priority: Critical
>
> As a user, I would like to see the changes that are included in a particular
> version. More specifically, if I'm on an old version and I upgrade to a
> version written by someone else, I have no way to know what changes occurred
> during that version upgrade.
> A simple solution would be to utilize the same logic which displays the
> current differences between local and stored in the registry and use that to
> show the differences between the current version N and version N-1. The user
> could then change between versions to see the changes that happened as part
> of that version.
> An even better solution (from a DFM perspective) would be to be able to see
> the changes within any version (not just the most recent). That way a DFM
> wouldn't have to stop the flow for an extended period of time to view the
> changes/differences in different versions but I think that'd be more work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
