Skip to content

Conversation

@corneliusroemer
Copy link
Member

Not cleaned up - I don't have the time to make a nice PR right now. Maybe @jameshadfield you can copy/paste what you'd be happy to use wherever you'd like to use it. For now we just use this branch locally with npm run start as it works well enough.

Description of proposed changes

Grab bag of fixes/changes that @marie3003 and I used to help us debug the JSON produced by some MLR modelling code.

We got uninformative error messages that didn't make it obvious what the issue was, for example just this: Error during file reading / parsing: Cannot read properties of undefined (reading 'get').

We got Claude to help us improve validation and error messages to make it faster to find issues in the JSON one uploads.

Now one gets nice console errors and stack traces:
Google Chrome 2025-10-10 16 05 01

We also ran into a (new?) macOS issue where you can't actually drag&drop from Finder, so we worked around that by adding a file picker.

Checklist

  • Checks pass
  • Update changelog

Copy link
Member

@jameshadfield jameshadfield left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The drag-and-drop page is essentially for development only, although perhaps some people may be using the GitHub pages version of it, so the functionality added here seems fine as-is.

I'll track down some new-ish datasets to confirm the changes here don't affect them.

Do you have some problematic JSONs which the error handling helped with here? Could you paste them somewhere on slack so I can test?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants