IQSS / IQSS/dataverse-frontend
Manage the use of custom html
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Currently the Dataverse UI has several places where the user is allowed to input custom html - for example in Dataverse and Dataset descriptions and other metadata fields, as well as with some previewers.
We want to avoid injecting html directly into the SPA, so for the MVP SPA implementation we will convert the custom html into markup.
However we need to investigate further all the usages of custom html in the Harvard Dataverse and other installations, to come up with a comprehensive plan for dealing with it.
This issue is for summarizing the current usage of custom html, and deciding how or if we want to support it in the new frontend post-MVP
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by cataloging custom HTML usage in Dataverse and Dataset descriptions, other metadata fields, and previewers; document the current cases and produce a comprehensive post-MVP support plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100