Move world generation hardcoded constants to config.yaml #56

Open
opened 2026-03-14 23:57:23 +00:00 by freemo · 0 comments
Owner

Metadata

  • Commit Message: refactor(worldgen): make world generation parameters configurable via config.yaml
  • Branch: feature/m3-v11-worldgen-config

Background

RESOLUTION_METRES, MAX_TILES, lat/lon ranges, and thread counts are hard-coded constants. There are no config.yaml entries for world generation.

Expected Behavior

ServerConfig keys override constants: world_resolution_metres, world_max_tiles, world_lat_range, world_lon_range, world_max_download_threads, world_max_process_threads.

Acceptance Criteria

  • Generator reads parameters from ServerConfig with fallback to constants
  • config.yaml includes new keys with defaults matching current constants
  • Spec updated with config key table

Subtasks

  • Add config keys to conf/config.yaml
  • Update WorldCoverGenerator constructor to read from ServerConfig
  • Tests: Unit tests for config override behavior
  • Run bundle exec rake unit, fix any errors

Definition of Done

This issue is complete when all subtasks are done, commit created on the specified branch, PR submitted and merged.

## Metadata - **Commit Message**: `refactor(worldgen): make world generation parameters configurable via config.yaml` - **Branch**: `feature/m3-v11-worldgen-config` ## Background `RESOLUTION_METRES`, `MAX_TILES`, lat/lon ranges, and thread counts are hard-coded constants. There are no config.yaml entries for world generation. ## Expected Behavior `ServerConfig` keys override constants: `world_resolution_metres`, `world_max_tiles`, `world_lat_range`, `world_lon_range`, `world_max_download_threads`, `world_max_process_threads`. ## Acceptance Criteria - [ ] Generator reads parameters from `ServerConfig` with fallback to constants - [ ] `config.yaml` includes new keys with defaults matching current constants - [ ] Spec updated with config key table ## Subtasks - [ ] Add config keys to `conf/config.yaml` - [ ] Update `WorldCoverGenerator` constructor to read from `ServerConfig` - [ ] Tests: Unit tests for config override behavior - [ ] Run `bundle exec rake unit`, fix any errors ## Definition of Done This issue is complete when all subtasks are done, commit created on the specified branch, PR submitted and merged.
freemo added this to the v1.1.0 milestone 2026-03-14 23:57:23 +00:00
freemo self-assigned this 2026-03-15 04:25:22 +00:00
freemo modified the milestone from v1.1.0 to v1.2.0 2026-03-16 00:28:09 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
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.

Reference: aethyr/Aethyr#56
No description provided.