Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

AppBase events and their order are not documented

Open Beginner friendly
#9,769 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
documentation

Research direction

The events are fired in src/framework/app-base.js, at the line ranges listed in the issue (for example start, initialize and update near lines 1086 and 1179). Read how the Asset and ButtonComponent classes document their events with @event JSDoc and static EVENT_ constants, then do the same for AppBase. Done means each fired event has an @event entry or constant, and the update-order note is written down. Whether to add a postupdate event is a separate question for maintainers and is not required here.

Written by the indexing model from the issue text.

Description

The application fires a number of events, but none of them are documented - there is no @event JSDoc and no static EVENT_* constant on AppBase, so the API reference does not list them. Other framework classes document theirs this way, for example Asset and ButtonComponent.

The events AppBase fires:

Their order relative to the components is only visible in the source. For example, the update event fires after every component's update, animationUpdate and postUpdate:

https://github.com/playcanvas/engine/blob/bf6b6e7efe5faefd5dcf789ef7250e2be002a96b/src/framework/app-base.js#L1163-L1179

There is no postupdate event. Code expecting one, for example to adjust a camera after the frame's updates, gets no warning: app.on('postupdate', ...) subscribes and never fires.

Dominant language
JavaScript
Stars
17k
Forks
2k
Avg merge
4h 21m
Merged PRs (30d)
286

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 playcanvas/engine

All issues in playcanvas/engine

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.