allow file drop while load file modal is open

[interim17]

Time estimate or Size

How long do you expect it to take a reviewer to review this PR?
Alternately, is this PR xsmall, small, medium, large, or xlarge?

Problem

What is the problem this work solves, including
Link to story or ticket

Solution

What I/we did to solve this problem

with @pairperson1

Type of change

Please delete options that are not relevant.

• 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)
• This change requires a documentation update
• This change requires updated or new tests

Change summary:

• Tidy, well formulated commit message
• Another great commit message
• Something else I/we did

Steps to Verify:

1. A setup step / beginning state
2. What to do next
3. Any other instructions
4. Expected behavior
5. Suggestions for testing

Screenshots (optional):

Show-n-tell images/animations here

Keyfiles (delete if not relevant):

1. main file/entry point
2. other important file

Thanks for contributing!

[github-actions]

Coverage report

❌ An unexpected error occurred. For more details, check console

Error: The process '/opt/homebrew/bin/npx' failed with exit code 1

Statements coverage not met for src/state/trajectory/selectors/index.ts: expected >=100%, but got 62.5%

St.❔	Category	Percentage	Covered / Total
🟡	Statements	69.7%	161/231
🔴	Branches	50%	19/38
🔴	Functions	42.55%	20/47
🟡	Lines	69.19%	137/198

Test suite run failed

Failed tests: 0/18. Failed suites: 6/8.

  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/runner/work/simularium-website/simularium-website/node_modules/lodash-es/lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

    > 1 | import { isString } from "lodash";
        | ^
      2 | import queryString from "query-string";
      3 |
      4 | import {

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.require (src/util/userUrlHandling.ts:1:1)
      at Object.require (src/util/test/index.test.ts:18:1)

---

  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/runner/work/simularium-website/simularium-website/node_modules/lodash-es/lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

       5 | import { ArgumentAction } from "redux-logic/definitions/action";
       6 | import queryString from "query-string";
    >  7 | import { map, reduce } from "lodash";
         | ^
       8 | import { v4 as uuidv4 } from "uuid";
       9 | import {
      10 |     ErrorLevel,

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.require (src/state/trajectory/logics.ts:7:1)
      at Object.require (src/state/trajectory/index.ts:2:1)
      at Object.require (src/state/index.ts:15:1)
      at Object.require (src/state/selection/selectors/selectors.test.ts:1:1)

---

  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/runner/work/simularium-website/simularium-website/node_modules/lodash-es/lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

       5 | import { ArgumentAction } from "redux-logic/definitions/action";
       6 | import queryString from "query-string";
    >  7 | import { map, reduce } from "lodash";
         | ^
       8 | import { v4 as uuidv4 } from "uuid";
       9 | import {
      10 |     ErrorLevel,

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.require (src/state/trajectory/logics.ts:7:1)
      at Object.require (src/state/trajectory/index.ts:2:1)
      at Object.require (src/state/index.ts:15:1)
      at Object.require (src/containers/ViewerPanel/selectors.test.ts:1:1)

---

  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/runner/work/simularium-website/simularium-website/node_modules/lodash-es/lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

       5 | import { ArgumentAction } from "redux-logic/definitions/action";
       6 | import queryString from "query-string";
    >  7 | import { map, reduce } from "lodash";
         | ^
       8 | import { v4 as uuidv4 } from "uuid";
       9 | import {
      10 |     ErrorLevel,

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.require (src/state/trajectory/logics.ts:7:1)
      at Object.require (src/state/trajectory/index.ts:2:1)
      at Object.require (src/state/index.ts:15:1)
      at Object.require (src/containers/ModelPanel/selectors.test.ts:2:1)

---

  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/runner/work/simularium-website/simularium-website/node_modules/lodash-es/lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      1 | import { createSelector } from "reselect";
      2 | import { UIDisplayData } from "@aics/simularium-viewer";
    > 3 | import { isEqual } from "lodash";
        | ^
      4 |
      5 | import { getDefaultUIDisplayData } from "../trajectory/selectors";
      6 | import {

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.require (src/state/compoundSelectors/index.ts:3:1)
      at Object.require (src/state/compoundSelectors/compoundSelectors.test.ts:1:1)

---

  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/runner/work/simularium-website/simularium-website/node_modules/lodash-es/lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

       5 | import { ArgumentAction } from "redux-logic/definitions/action";
       6 | import queryString from "query-string";
    >  7 | import { map, reduce } from "lodash";
         | ^
       8 | import { v4 as uuidv4 } from "uuid";
       9 | import {
      10 |     ErrorLevel,

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.require (src/state/trajectory/logics.ts:7:1)
      at Object.require (src/state/trajectory/index.ts:2:1)
      at Object.require (src/state/index.ts:15:1)
      at Object.require (src/state/trajectory/selectors/selectors.test.ts:1:1)

Report generated by 🧪jest coverage report action from 8f7a1f4