ARTIST-Association / ARTIST-Association/CANVAS

Proposal: Switch to relative imports

Open
#94 0 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
Python
Stars
6
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Right now, every file is mapped via the `jsconfig.json` and the import map in `editor.hmtl`, so for each new file a new entry is needed.
+ Leads to bigger files, to save entries
+ Leads to merge conflicts as these files tend to be shared across branches

But relative imports on the other hand can get pretty big and ugly -> define a view base paths, like @sidebar/*, @editor/* etc and use relative imports from there _(our Js code is propably not structured enough for this)_

Contributor guide

Open the contributing guide

Research direction

Start by reading jsconfig.json and the import map in editor.hmtl, then inspect how current JavaScript imports are organized. Determine whether a consistent view-base-path structure is feasible and document the agreed import approach and affected files as done.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.