A base Compare view is implemented. This issue tracks more todos, questions, etc. as we're integrating server-side into the app.
There is an upload button to allow any user (i.e. no login required, no metadata, not even a EUF header) to compare their data against available data.
Query criteria (intersection, difference, etc.) and implementation TBD, see #37
A clear and concise description of todo items.
Compare View tasks
Functionality
[x] There is a minimal working upload, but we need to decide how to handle upload vs. selection (i.e not both), server-side details, API URL handling in component via service, etc. We also need to handle file cleaning on the system.
[x] Because props are passed down to CompareStep components, which may be undefined when the child component is mounted, we have to somehow handle this. This is purely a timing issue. I'm using something like
doesn't seem like the best way to handle this. There are too many options, I don't know what is best, besides I haven't managed to make all of them work e.g.async (in combination with Suspense, which is currently still an experimental feature), async components, etc. Maybe something like <child-component @vnodeMounted="doSomething" /> would work? There are many resources, but none is definitely useful... check also Better support for top-level await in Githubissues.
Githubissues is a development platform for aggregating issues.
Aims/objectives.
A base Compare view is implemented. This issue tracks more todos, questions, etc. as we're integrating server-side into the app.
A clear and concise description of todo items.
Compare View tasks
Functionality
doesn't seem like the best way to handle this. There are too many options, I don't know what is best, besides I haven't managed to make all of them work e.g. async (in combination with
Suspense, which is currently still an experimental feature), async components, etc. Maybe something like<child-component @vnodeMounted="doSomething" />would work? There are many resources, but none is definitely useful... check also Better support for top-level await in Githubissues.