refactor(research): refactoring upload submit modals to remove some duplication

[codisart]

PR Checklist

• - Commit messages are descriptive, it will be used in our Release Notes

PR Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Developer experience (improves developer workflows for contributing to the project)

Description

What this PR does

Breakdown the upload status modal into several smaller components to remove duplication and to allow better readibility

---

What happens next?

Thanks for the contribution! We try to make sure all PRs are reviewed ahead of our monthly maintainers call (first Monday of the month)

If the PR is working as intended it'll be merged and included in the next platform release, if not changes will be requested and re-reviewed once updated.

If you need more immediate feedback you can try reaching out on Discord in the Community Platform development channel.

[benfurber]

Hey @codisart, I can see the unit test is failing.

Another thought. There's probably some duplication with the HowToSubmitStatus. Could a SubmitStatus component be created they could both have as a parent? Similar to either the layout/styling only and/or store access in #3356.

[codisart]

Hey @codisart, I can see the unit test is failing.

Another thought. There's probably some duplication with the HowToSubmitStatus. Could a SubmitStatus component be created they could both have as a parent? Similar to either the layout/styling only and/or store access in #3356.

Yes you right. Where I should put the common component ? In the packages/components folder ?

[benfurber]

Hey @codisart, I can see the unit test is failing.
Another thought. There's probably some duplication with the HowToSubmitStatus. Could a SubmitStatus component be created they could both have as a parent? Similar to either the layout/styling only and/or store access in #3356.

Yes you right. Where I should put the common component ? In the packages/components folder ?

Both? :) At least one. For design/layout stuff, aim for the components library. Stuff that's linked to the stores, etc. for common.

Looking at the specifics here. I'd say component library. There's a command in the readme for generating a new component with a story and test files.