Repository navigation
Let pharo be a domain of its own - #46
Merged
Merged
Conversation
What Pharo says about itself - the image half and the virtual machine half - used to be two domains at the root, and the deployed name pharo_image_… came out of a prefix the endpoint had been configured with. That configuration was a second description of the same tree, kept next to it, free to disagree with it. Now both hang under the domain #pharo. A series is named after the path to its node, so the deployed names fall out of the structure and an unconfigured handler writes them by itself. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The three tests named what registerImageMetrics and its siblings put at the root. That is one level deeper now, so they say so: the domain is #pharo, and the image and virtual machine halves are its children. Co-Authored-By: Claude Opus 5 (1M context) <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
1 participant
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.
What Pharo says about itself - the image half and the virtual machine half - used to be two domains at the root, and the deployed name pharo_image_… came out of a prefix the endpoint had been configured with. That configuration was a second description of the same tree, kept next to it, free to disagree with it.
Now both hang under the domain #pharo. A series is named after the path to its node, so the deployed names fall out of the structure and an unconfigured handler writes them by itself.