[desk-tool] Refactor file organization (chore)

[mariuslundgard]

Type of change (check at least one)

• 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 not work as expected)
• Documentation (fix or update to documentation)
• Maintenance
• Other, please describe: Code/file reorganizationo

Does this change require a documentation update? (Check one)

• Yes
• No

Current behavior

n/a

Description

These changes include moving around React components and CSS files to fit into the following structure:

@sanity/
  desk-tool/
    src/
      components/
        # All React components that are used in multiple places (panes)
      panes/
        # The various distinct panes that can be rendered by the Desk tool
      tool/
        # The root React component for the Desk tool

Note for release

n/a

Checklist

• I have read the Contributing Guidelines
• The PR title is appropriately formatted: [some-package] PR title (#123)
• The code is linted
• The test suite is passing
• Corresponding changes to the documentation have been made

[vercel]

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/sanity-io/test-studio/aek25sact
✅ Preview: https://test-studio-git-desk-tool-organize-pane-directory-chore.sanity-io.now.sh

[rexxars]

Looks good to me 👍

[vicmeow]

Looks good, but isn't it nicer to keep CSS files in a styles folder so that the components folder doesn't get too cluttered/long?

[mariuslundgard]

isn't it nicer to keep CSS files in a styles folder so that the components folder doesn't get too cluttered/long?

@vicbergquist I changed that because I find it quicker to jump between the CSS file and the JS file if they are in the same directory. I consider both CSS and JS to be the component, so think it should be in one place. If components list gets too long, it can be divided into subfolders?

[vicmeow]

isn't it nicer to keep CSS files in a styles folder so that the components folder doesn't get too cluttered/long?

@vicbergquist I changed that because I find it quicker to jump between the CSS file and the JS file if they are in the same directory. I consider both CSS and JS to be the component, so think it should be in one place. If components list gets too long, it can be divided into subfolders?

@mariuslundgard ok makes sense! 👍

[mariuslundgard]

Good! If we later find that using styles directories was better, we can always go back. Or better yet – we are on styled-components by then :)