search

IQSS / dataverse-frontend

An upcoming and modernized UI for Dataverse
Apache License 2.0
20 stars 16 forks source link

Edit Collection page #549

Open g-saracca opened 1 week ago

g-saracca commented 1 week ago

What this PR does / why we need it:

Adds the edit collection page in the SPA. Reuses the form to create a collection with a few refactors to be able to work for both modes (create and edit).

Which issue(s) this PR closes:

Special notes for your reviewer:

This can be reviewed as it is now, but for QA purposes I would wait until these two issues are merged first:

Suggestions on how to test this:

Step 1: Run the Development Environment

  1. Execute npm i.
  2. Navigate with cd packages/design-system && npm i && npm run build.
  3. Return with cd ../../.
  4. Ensure you have a .env file similar to .env.example, with the variable VITE_DATAVERSE_BACKEND_URL=http://localhost:8000.
  5. Navigate with cd dev-env.
  6. Start the environment using ./run-env.sh unstable.
  7. To verify the environment, visit http://localhost:8000 and check your local Dataverse installation.

Step 2: Test the feature Create subcollections and edit them, go to edit them again and validate that the fields are changed. Validate that works similar as in the JSF version. Also validate that when editing the root collection the form also looks the same way as in JSF.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

No, pretty much the same UI from the create collection page.

Is there a release notes update needed for this change?:

No

Additional documentation:

No

coveralls commented 1 week ago

Coverage Status

coverage: 97.754% (+0.2%) from 97.561% when pulling c836d0e64542d3f58be57725bdc08e63487570ca on feat/545-edit-collection-page into 53a6a3f7e014ea34024597ee3f8f3bc507f04759 on develop.