Skip to content

UX: Generator output shows misleading paths for generated files #28

Closed

Description

@apotema

Current Behavior

When labelle generate runs, it shows output like:

Generating for target 'raylib_desktop':
  - raylib_desktop/main.zig
  - raylib_desktop/build.zig
  - raylib_desktop/build.zig.zon
Generation complete!

This suggests the files are in raylib_desktop/ relative to the project root, but they're actually in .labelle/raylib_desktop/.

Expected Behavior

The output should show the actual paths:

Generating for target 'raylib_desktop':
  - .labelle/raylib_desktop/main.zig
  - .labelle/raylib_desktop/build.zig
  - .labelle/raylib_desktop/build.zig.zon
Generation complete!

Or at minimum, indicate the base directory:

Generating for target 'raylib_desktop' in .labelle/:
  - main.zig
  - build.zig
  - build.zig.zon
Generation complete!

Impact

  • New users might look for files in the wrong location
  • CI scripts need to know the actual path structure
  • Documentation needs to explain the .labelle/ prefix

Related

This caused confusion during CI integration testing where we initially tried to cd to raylib_desktop/ instead of .labelle/raylib_desktop/.

Reference: labelle-engine CI workflow setup

Activity

  1. apotema commented on Apr 17, 2026

    @apotema
    ContributorAuthor

    Closing as obsolete — the generator output format described here no longer exists. After the assembler split (#150), today's labelle generate emits:

    labelle: generating 'flying_platform'...
      backend: sokol  platform: desktop  ecs: zig_ecs  gui: imgui  window: 1024x768
    labelle-assembler: generated .labelle/sokol_desktop/
    

    No per-file listing with misleading relative paths. The specific bug described is gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions