Support for Hot-reloading

Open
#3,454 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
dart, flutter

Research direction

No files, tests, or entry points are identified. Start by reviewing how Flame components are structured and how Flutter widgets handle hot reload, then define the required behavior and performance constraints. Done requires an agreed implementation scope and evidence that hot reload updates components without adversely affecting performance or component size.

Written by the indexing model from the issue text.

Description

enhancement
Problem to solve

Hot-reload support would increase flame developer efficiency and possibly also adoption. Support for hot-reloading shouldn't adversely affect performance or size of components.

Proposal

Components handle hot-reload information and update accordingly, as done by flutter widgets. More details to come.

More information

No response

Other
  • Are you interested in working on a PR for this?
Dominant language
Dart
Stars
10.8k
Forks
1.1k
Avg merge
2d 4h
Merged PRs (30d)
61

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flame-engine/flame

All issues in flame-engine/flame

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.