Should `async_resources` be updated manually when other async components are added?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, python
- Domain
- build-system, frontend
Research direction
Reproduce the issue by copying the cookiecutter component, renaming it, and exporting the new component in the stated places. Inspect init.py and the dash-generate-components entry point, then verify whether async-NewComponent*.js is generated and discoverable by the browser without manual updates to async_resources.
Written by the indexing model from the issue text.
Description
Hi,
I started trying my way around async components and I was having some issues when I added a second component to the library. To reproduce it, just copy the one created by cookiecutter, refactor the name to something else and export it in the right places...
The issue was somehow related to the browser not finding async-NewComponent*.js, so I realized that __init__.py has an async_resources list containing just the component created automatically by cookiecutter, and not NewComponent just created.
As I asked in the title, should this list be modified manually or is it expected that dash-generate-components should do the trick?
Thanks!
- Dominant language
- Python
- Stars
- 294
- Forks
- 196
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from plotly/dash-component-boilerplate
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
plotly/dash-component-boilerplate#173 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
plotly/dash-component-boilerplate#170 · 1 comment ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
plotly/dash-component-boilerplate#166 · 1 reaction ·
-
Running build Open
Difficulty 3/5 1-2 days Newbie friendliness 30/100
All issues in plotly/dash-component-boilerplate
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/skills#1811 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
speaches-ai/speaches#678 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
datalayer/mcp-compose#42 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
UKGovernmentBEIS/inspect_evals#2523 ·