feat(ui-debug): add unsupported files handling

[hdinia]

ANT-2362 => handle unsupported files display
ANT-2529 => display output matrices as raw text

[skamril]

By convention, lower case are used for object keys, even for a constant

[hdinia]

For this type of constant object where both the object name and its keys represent fixed values or schemes, it's more conventional to have both in UPPER_SNAKE_CASE, it's not a regular enum-like object see: https://google.github.io/styleguide/tsguide.html#naming

[skamril]

Your link said like me lol https://google.github.io/styleguide/tsguide.html#identifiers-constants

const URL_SCHEMES = {
  matrix: ...,
  ...
}

[hdinia]

I know its confusing, the style guide example uses lowercase because they're dealing with actual unit names rather than symbolic constants.

The difference is that:

In URL_SCHEMES, the keys (MATRIX, JSON, FILE) are symbolic identifiers representing categories/types
In UNIT_SUFFIXES, the keys ('milliseconds', 'seconds') are the actual string names of time units

look at "Rules by identifier type" section:
says: "CONSTANT_CASE global constant values, including enum values. See Constants below."

[hdinia]

we should create a ticket and spend time to make our set of rules, especially for this kind of conventions

[hdinia]

for a more general example:

1. When keys are symbolic constants (use UPPER_SNAKE_CASE):

const ERROR_CODES = {
    NOT_FOUND: 404,
    SERVER_ERROR: 500,
    UNAUTHORIZED: 401
};

Here, NOT_FOUND is a symbolic name representing the concept of a "not found" error. The key itself is a symbol/identifier.

2. When keys are actual VALUES/NAMES (use lowercase):

const MIME_TYPES = {
    'image/jpeg': '.jpg',
    'image/png': '.png',
    'text/html': '.html'
};

Here, 'image/jpeg' is the actual MIME type string that would be used in HTTP headers.

Think of it this way:

• If you're using the key as a reference/symbol (like URL_SCHEMES.MATRIX), use UPPER_SNAKE_CASE
• If you're using the key as a literal value (like MIME_TYPES['image/jpeg']), use lowercase

[skamril]

Alright! I didn't know this subtlety.

[skamril]

Like I had already said to you, use treeData.toLowerCase().endsWith(ext), because extension are case insensitive, .txt and .TXT are both valid, an user can import file with uppercase extension!

[hdinia]

mybad, its fixed

[skamril]

"ouput" value has been forgotten:

return path.split("/")[0] === "output";

[skamril]

Or rename isInOuputFolder

[hdinia]

it's intended I'll rename it to better reflect the purpose

[skamril]

Better to parse in the usePromiseWithSnackbarError to make it once

[hdinia]

at this point their no possible error

[skamril]

Yes the error it's for the API call, but I said to had directly after the call to memoized the value.

() => getStudyData<string>(studyId, filePath).then(text => parseContent(text, { filePath, fileType })):
...
deps: [studyId, filePath, fileType],

[hdinia]

ok I will see that

[hdinia]

indeed its good like this, done