Document front end coding standards for imports

[seancolsen]

• Relative vs absolute
• When to use aliases
• @mathesar-component-library vs @mathesar-component-library-dir
• When to add new code to a index.ts

[seancolsen]

Here's a start at some content

Imports

The following rubric helps keep our imports clean and easy to refactor:

• When possible, import symbols from a high-level index.ts file instead of from more deeply nested files.

  • Good ✅

    import { getTabularContent } from '@mathesar/stores/table-data';

  • Bad ❌

    import { getTabularContent } from '@mathesar/stores/table-data/manager';

I think the rest of the content can probably follow the same pattern.

I'm having trouble writing the rest of it though because I only have a vague sense of the rules. This has come up many times in review of my PRs, so it would be helpful for me to have some documentation like this to follow.

@pavish would you be up for finishing this content?

[pavish]

@seancolsen Yes, I'll come up with the content.

[github-actions]

This issue has not been updated in 90 days and is being marked as stale.

[github-actions]

This issue has not been updated in 90 days and is being marked as stale.

[seancolsen]

I'm closing this since it's very old.