[
https://issues.apache.org/jira/browse/NIFIREG-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326671#comment-16326671
]
Danny Lane commented on NIFIREG-77:
-----------------------------------
I've added a WIP commit here is anyone would like to offer feedback before I
submit a PR?
https://github.com/dannylane/nifi-registry/commit/eeed846167dc90d983ea1d37d4149980b3057be2
I tried to go with the API returning the existing diff classes but each
{{FlowDifference}} contains references to before/after versions of the
components and they got serialized in the API response which I though was a bit
much.
I added a couple of classes to the model module to act as the response form the
API (they are essentially {{Dto}} s but I didn't use that naming convention as
I didn't see it used in the registry project).
The behavior is very similar to how NiFi gathers it's changes for the 'Show
Local Changes' functionality at the moment.
Happy to make changes if this is way off base...
> 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
> Attachments: Suggestion for diff UX.png
>
>
> 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
(v7.6.3#76005)
