-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import feature: show the differences of an element when it is updated by an import (and refactor) #810
Conversation
46365bd
to
052c154
Compare
d8dbae1
to
6cc0dbd
Compare
ca32db7
to
d10fa87
Compare
98b7154
to
04d332a
Compare
f797f10
to
c35469e
Compare
55379af
to
8995ac2
Compare
267f5b1
to
21722cc
Compare
|
I am sorry, there is more work to do on the css. Paddings and margins are off all over the place. |
Signed-off-by: David Wallace <[email protected]>
Signed-off-by: David Wallace <[email protected]>
Signed-off-by: David Wallace <[email protected]>
Signed-off-by: David Wallace <[email protected]>
Signed-off-by: David Wallace <[email protected]>
038ee3f
to
550aeb5
Compare
rebased to dev-2.2.0 and force pushed |
I think new is great since we use new/neu also in the interface. |
Signed-off-by: David Wallace <[email protected]>
Signed-off-by: David Wallace <[email protected]>
ok, changed the text to "new" |
Sorry I found more bugs:
with this xml
(GitHub does not allow XML uploads)
after I click Question or click show. I think this is also because of the broken xml file, so it is not super important.
|
… at save Signed-off-by: David Wallace <[email protected]>
…or builUri Signed-off-by: David Wallace <[email protected]>
thanks for noticing and the xml.
This came from the back-end. I've changed it now so that "new" and "create" will not show at import when there are errors (and the db instance won't be saved anyways).
I've removed the onClick from the badge. One other issue with this faulty xml was that the Another mini-feature addition I thought about was, to make these URIs at import also clickable (so that they open the edit page of each element, like in management). I would just need to the |
No I would not add that. It could lead to problems if the users then go back in the browser. They should just click on "Back". |
|
Signed-off-by: David Wallace <[email protected]>
Signed-off-by: David Wallace <[email protected]>
Description
This PR implements a text difference viewer for the import of RDMO content elements (catalogs, optionsets, etc..).
It uses the react-diff-viewer-continued to display the changes during an import. In the back-end a sort of "track changes" function tracks the current and new state of each element which is returned in the json response.
The code architecture of the import is refactored into one central import function under
management
with helpers for each type of element.Related issues: #468, #469
Includes bug fix for: #998
Motivation and Context
How has this been tested?
Screenshots (if appropriate)
Currently:
previous version
![management-import-optionsets-1-changes](https://github.com/rdmorganiser/rdmo/assets/13996213/e5fcb01c-bc8e-4c86-9b89-4318fd015c47)older previous version
![management-import-optionsets-1-changes](https://github.com/rdmorganiser/rdmo/assets/13996213/afec9fae-839b-496f-a817-5329f4167a45)Types of Changes
Checklist
Still todo
Front-end