Skip to content

Conversation

@seddonym
Copy link
Collaborator

@seddonym seddonym commented Dec 2, 2025

Replaced by #267 which has a narrower scope.

Prior to this, subsequent sibling packages in the contents string would
be incorrectly nested under the directory the line above, due to an
assumption that the contents string would be dedented. This takes
account of that.
This doesn't change the implementation yet, but it prepares us for
supporting namespace packages passed in.
This pushes the NamespacePackageEncountered error up
the call stack into the use case.
Also switch to using abstract types as parameters
@seddonym seddonym force-pushed the arbitrary-root-packages branch from 7492153 to 0fcea6d Compare December 3, 2025 15:55
@seddonym seddonym closed this Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants