-
Notifications
You must be signed in to change notification settings - Fork 20
Collection Page: convert html to markdown in description field #608
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
Conversation
g-saracca
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good! Just 2 minor comments
g-saracca
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving, thanks!
|
test/e2e is failing on this - please advise :) |
|
@ofahimIQSS I think this is a timing issue - the csv file has be ingested and converted to a tab-delimited file, which I think happens asynchronously on the server side. (I ran it locally and can't reproduce the error.)I updated the test to check the filterBy using text files, which don't have to be ingested. |
|
testing passed but need confirmation on why the UI review and tests are pending |
|
@ofahimIQSS All UI Reviews passing. |
What this PR does / why we need it:
The Get Collection use case in js-dataverse was updated to return the html in the description field, rather than markdown. This PR converts the html returned from js-dataverse into markdown for the Collection Page. (In Edit Collection Page, it will show the original html).
Which issue(s) this PR closes:
Special notes for your reviewer:
This change depends on a js-dataverse PR IQSS/dataverse-client-javascript#265. When that PR is approved, package.json should be updated to use the alpha version of the library.
Suggestions on how to test this:
Step 1: Run the Development Environment
Execute npm i.
Navigate with cd packages/design-system && npm i && npm run build.
Return with cd ../../.
Ensure you have a .env file similar to .env.example, with the variable VITE_DATAVERSE_BACKEND_URL=http://localhost:8000.
Navigate with cd dev-env.
Start the environment using ./run-env.sh unstable.
To verify the environment, visit http://localhost:8000/ and check your local Dataverse installation.
Step 2: Test the feature
Create a Collection and add html in the description field. The Collection Page should show the rendered html. Go to Edit Collection Page. It should show the original html that was submitted.