Repository navigation
fix(add): a solution's local run is its own workspace, not a playground - #1237
Merged
Merged
Conversation
I invented a layout. The scaffold wrote the local composition into a
playground/ subdirectory; no solution in the fleet is built that way.
A PLAYGROUND IS A MODULE'S — somewhere to exercise a module on its own.
Two solutions carry one as an extra, and reading those two as the
pattern is exactly the confusion between a playground and a solution
that this repeats every time it is made.
What nine of nine solutions actually do: the solution's own directory IS
the workspace. core-solutions has no root workspace at all, so
workspace.codefly.yaml sits beside module.codefly.yaml and the run
happens there.
So the composition moves to the solution root, `make playground` becomes
`make run`, and the generated doc is LOCAL.md beside it.
The subdirectory was also carrying a real bug: with the workspace one
level down the module path was "..", and moving the file up without
changing it resolved the module to the parent and failed the run on a
module.codefly.yaml that was not there. It is "." now, and a test holds
it to that.
Verified on a clean scaffold, `make run` from the solution root:
edge / 200
edge /v1/notes/overview 200
backend /assets/mf-manifest.json 200
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I invented a layout. The scaffold wrote the local composition into a
playground/subdirectory; no solution in the fleet is built that way.A playground is a module's
It is somewhere to exercise a module on its own. Two solutions carry one as an extra, and reading those two as the pattern is exactly the confusion between a playground and a solution that gets repeated every time.
What nine of nine solutions actually do — the solution's own directory is the workspace.
core-solutionshas no root workspace at all, soworkspace.codefly.yamlsits besidemodule.codefly.yaml:So the composition moves to the solution root,
make playgroundbecomesmake run, and the generated doc isLOCAL.mdbeside it.The subdirectory was carrying a real bug
With the workspace one level down the module path was
path: ... Moving the file up without changing it resolved the module to the parent and failed the run:It is
path: .now, and a test holds it to that — along with one that fails ifcd playgroundever reappears in the Makefile.Verified
Clean scaffold,
make runfrom the solution root:Docs updated:
docs/commands.md.🤖 Generated with Claude Code