Repository navigation
refactor: organize core source layout - #17
Merged
Merged
Conversation
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.
Summary
Reorganizes the internal
src/tree so high-level/public API implementations no longer sit loose at the source root.New layout
Changes
src/client.cpp->src/core/client.cppsrc/headers.cpp->src/core/headers.cppsrc/url.cpp->src/core/url.cpphttp/,net/, andplatform/architectural boundaries unchangedsrc/dummy.cppsrc/CMakeLists.txtsource pathsBehavior
No runtime/API behavior changes are intended. GitHub detects all three implementation moves as exact renames with zero content changes.
Rationale
The project is growing past the initial foundation stage. Keeping public/core implementation files at the
src/root makes future client state, redirect, and connection-reuse work harder to navigate. A dedicatedcore/layer makes the physical source layout match the architectural separation already documented in the repository.Follow-up
A separate PR will tighten GitHub Actions path filters so documentation-only changes do not run the full C++ build/test matrix.