dandi / dandi/dandi-archive

Consider not mutating schema in client

Open
#2,190 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
26
Forks
21
Avg merge
4d 23h
Merged PRs (30d)
15

Description

Currently we dynamically remove the `description` field in the schema in the client. We should consider fixing the schema upstream and/or instrumenting VJSF to just ignore that field instead of mutating the schema.

https://github.com/dandi/dandi-archive/blob/f602e675283ce15bddb67078fdf93b7bced3045b/web/src/components/Meditor/utils.ts#L30-L32

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at web/src/components/Meditor/utils.ts lines 30-32 and trace how the schema reaches VJSF. Determine whether the upstream schema or VJSF should own ignoring the description field; done means the client no longer mutates the schema while the field is handled as intended.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.