aethyr/Aethyr
2
0
Fork 0
Code Issues 281 Pull requests Projects Releases Packages Wiki Activity Actions

Implement extension auto-discovery scanner #75

New issue
Open
opened 2026-03-14 23:57:28 +00:00 by freemo · 0 comments
freemo commented 2026-03-14 23:57:28 +00:00
Owner
Copy link

Metadata

  • Commit Message: feat(extensions): implement extension auto-discovery scanner
  • Branch: feature/m3-extension-scanner

Background and Context

The extension system under lib/aethyr/extensions/ currently requires hardcoded require statements in core files like login.rb and player.rb to load extension code. The specification calls for an auto-discovery scanner that finds and loads extensions at startup without requiring modifications to core engine files.

Expected Behavior

An ExtensionScanner class scans lib/aethyr/extensions/ subdirectories (actions/commands/, input_handlers/, objects/, skills/, flags/, reactions/, help/) and automatically requires all .rb files found. The scanner runs during server boot, after core code is loaded but before the first player connects.

Acceptance Criteria

  • Extensions are discovered and loaded automatically from the extensions directory tree
  • No hardcoded require statements for extensions exist in core engine files
  • Loading order handles dependencies (objects before commands that reference them)
  • Extension load failures are logged but do not crash the server
  • The scanner reports the count of loaded extensions at startup

Subtasks

  • Code: Create lib/aethyr/core/util/extension_scanner.rb with an ExtensionScanner class
  • Code: Implement scan(base_path) method that recursively finds all .rb files under the given path
  • Code: Implement a directory ordering strategy: load objects/ before actions/ and input_handlers/ to ensure class dependencies are met
  • Code: Wrap each require in a begin/rescue block that logs errors but allows other extensions to load
  • Code: Integrate the scanner into the server boot sequence in lib/aethyr/core/components/manager.rb or the main Aethyr.main method
  • Code: Log a summary of loaded extensions (count per category) at INFO level
  • Docs: Add RDoc documentation to the ExtensionScanner class explaining the scan order and error handling
  • Docs: Update the Docusaurus extension development guide with instructions on how auto-discovery works
  • Tests (Cucumber): Add tests/unit/extension_scanner.feature covering: scanner finds files in subdirectories, scanner handles empty directories, scanner logs errors for invalid files, scanner respects load order
  • Tests (Cucumber Integration): Add integration feature verifying extensions are loaded when the server boots
  • Tests (Profiling): Run bundle exec rake unit_profile and verify no performance regressions in server boot time
  • Quality: Verify coverage >=85% via bundle exec rake unit. If coverage is <85% then review the current unit test coverage report at build/tests/unit/coverage/ and use it to write new Cucumber based unit tests to improve code coverage. Specifically, write Cucumber/Gherkin style unit tests that are descriptively named and specifically improve coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun bundle exec rake unit to verify all tests pass and coverage is above >=85%. Only mark this as complete once coverage is >=85%, if not repeat this task as many times as is needed until coverage reaches >=85%.
  • Quality: Run bundle exec rake (default task: unit tests with coverage) and bundle exec rake integration, fix any errors if needed ensuring both pass across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
## Metadata - **Commit Message**: `feat(extensions): implement extension auto-discovery scanner` - **Branch**: `feature/m3-extension-scanner` ## Background and Context The extension system under `lib/aethyr/extensions/` currently requires hardcoded `require` statements in core files like `login.rb` and `player.rb` to load extension code. The specification calls for an auto-discovery scanner that finds and loads extensions at startup without requiring modifications to core engine files. ## Expected Behavior An ExtensionScanner class scans `lib/aethyr/extensions/` subdirectories (actions/commands/, input_handlers/, objects/, skills/, flags/, reactions/, help/) and automatically requires all `.rb` files found. The scanner runs during server boot, after core code is loaded but before the first player connects. ## Acceptance Criteria - [ ] Extensions are discovered and loaded automatically from the extensions directory tree - [ ] No hardcoded require statements for extensions exist in core engine files - [ ] Loading order handles dependencies (objects before commands that reference them) - [ ] Extension load failures are logged but do not crash the server - [ ] The scanner reports the count of loaded extensions at startup ## Subtasks - [ ] Code: Create `lib/aethyr/core/util/extension_scanner.rb` with an `ExtensionScanner` class - [ ] Code: Implement `scan(base_path)` method that recursively finds all `.rb` files under the given path - [ ] Code: Implement a directory ordering strategy: load objects/ before actions/ and input_handlers/ to ensure class dependencies are met - [ ] Code: Wrap each `require` in a begin/rescue block that logs errors but allows other extensions to load - [ ] Code: Integrate the scanner into the server boot sequence in `lib/aethyr/core/components/manager.rb` or the main `Aethyr.main` method - [ ] Code: Log a summary of loaded extensions (count per category) at INFO level - [ ] Docs: Add RDoc documentation to the ExtensionScanner class explaining the scan order and error handling - [ ] Docs: Update the Docusaurus extension development guide with instructions on how auto-discovery works - [ ] Tests (Cucumber): Add `tests/unit/extension_scanner.feature` covering: scanner finds files in subdirectories, scanner handles empty directories, scanner logs errors for invalid files, scanner respects load order - [ ] Tests (Cucumber Integration): Add integration feature verifying extensions are loaded when the server boots - [ ] Tests (Profiling): Run `bundle exec rake unit_profile` and verify no performance regressions in server boot time - [ ] Quality: Verify coverage >=85% via `bundle exec rake unit`. If coverage is <85% then review the current unit test coverage report at `build/tests/unit/coverage/` and use it to write new Cucumber based unit tests to improve code coverage. Specifically, write Cucumber/Gherkin style unit tests that are descriptively named and specifically improve coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `bundle exec rake unit` to verify all tests pass and coverage is above >=85%. Only mark this as complete once coverage is >=85%, if not repeat this task as many times as is needed until coverage reaches >=85%. - [ ] Quality: Run `bundle exec rake` (default task: unit tests with coverage) and `bundle exec rake integration`, fix any errors if needed ensuring both pass across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.
freemo added this to the v1.1.0 milestone 2026-03-14 23:57:28 +00:00
freemo self-assigned this 2026-03-15 04:25:23 +00:00
freemo modified the milestone from v1.1.0 to v1.2.0 2026-03-16 00:28:14 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
feature/m2-headless-renderer
dependabot/bundler/rdoc-6.3.2
dependabot/bundler/rexml-3.2.5
dependabot/bundler/json-tw-2.3
inprogress
dependabot/bundler/rake-tw-13.0
No results found.
Labels
Clear labels   
Blocked

Cannot proceed, depends on unresolved issue

  
Duplicate

Issue is a duplicate of an existing one

  
MoSCoW/Could Have

Desirable but not necessary, included if time permits

  
MoSCoW/Must Have

Essential, project cannot ship without it

  
MoSCoW/Should Have

Important but not strictly essential

  
Points/1

Estimated effort: 1 story points

  
Points/13

Estimated effort: 13 story points

  
Points/2

Estimated effort: 2 story points

  
Points/21

Estimated effort: 21 story points

  
Points/3

Estimated effort: 3 story points

  
Points/5

Estimated effort: 5 story points

  
Points/8

Estimated effort: 8 story points

  
Priority/Backlog

Not yet prioritized

  
Priority/Critical

Must be addressed immediately

  
Priority/High

Important, should be completed soon

  
Priority/Low

Nice to have, not time-sensitive

  
Priority/Medium

Normal priority, valid and should be addressed

  
State/Completed

Issue resolved and all PRs merged

  
State/In progress

Someone is actively working on this issue

  
State/In review

Implementation complete, PR submitted for review

  
State/Paused

Work temporarily suspended, typically blocked

  
State/Unverified

Issue created but not yet reviewed by a maintainer

  
State/Verified

Maintainer confirmed valid and actionable

  
State/Wont Do

Deliberate decision not to address this issue

  
Type/Bug

A defect in existing functionality

  
Type/Epic

Large body of work broken into multiple issues

  
Type/Feature

A new capability or user story

  
Type/Legendary

Major strategic pillar composed of multiple Epics

  
Type/Task

Technical or administrative work (not bug or feature)

  
Type/Testing

Test-only work item (TDD, test infrastructure, coverage)

No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
Milestone
Clear milestone
No items
No milestone
v1.2.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
freemo
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#34 Epic: Extension auto-discovery and loading
aethyr/Aethyr
Reference: aethyr/Aethyr#75
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?