112 add front end coordinate file parsing functionality#142
112 add front end coordinate file parsing functionality#142joshnorlin wants to merge 50 commits intomainfrom
Conversation
There was a problem hiding this comment.
@joshnorlin I'll circle back to reviewing once the package issue is resolved.
c84fce4 to
1e95cb4
Compare
JosephPBaruch
left a comment
There was a problem hiding this comment.
This looks really great! Super impressed on how this came together and it worked super well. Just need a few organization changes and renaming to clear up some confusion.
| backgroundColor: theme.palette.mode === "dark" ? "rgba(100, 108, 255, 0.1)" : "rgba(100, 108, 255, 0.08)", | ||
| backgroundColor: | ||
| theme.palette.mode === "dark" | ||
| ? "rgba(100, 108, 255, 0.1)" |
There was a problem hiding this comment.
Colors like these are used often. Can we define this once and reuse? Perhaps store in the useTheme() hook?
JosephPBaruch
left a comment
There was a problem hiding this comment.
Looks like You're still working on some stuff so I wont say much. Looking good so far though. I'd say, the validator functions in helper are a bit too tied to the example files. These could be more general like checking a passed in "Total Grid Cells" count
ff0a74b to
5230ac1
Compare
- Fixed __dirname not defined by using import.meta.url with fileURLToPath - Updated all hard-coded fixture paths to use fixture() helper function - Added scrolling to MUI Dialog to find coordinate upload button - Tests now executing successfully (14 passing, 7 failing with error message validation issues) - Error message validation selectors need refinement for strict mode compliance
5230ac1 to
85935eb
Compare
This PR accomplishes the following: