Repository navigation
Conversation
754f164 to
badbcf4
Compare
de0d326 to
b7d03c3
Compare
|
Important Review skippedReview was skipped as selected files did not have any reviewable changes. ⚙️ Run configuration
📥 Commits
You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughPath utilities now recognize both slash characters and provide native-separator and filename helpers. File-system path handling uses the native separator, and map-name fallbacks use the shared filename helper. ChangesPath handling
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix · Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Out of Scope Changes check | The new public FileSystem::appendPathSeparator declaration and implementation are not used by either fallback path and do not support the MapCache::addMap fix for issue #3100. The related `isPathI… |
Remove FileSystem::appendPathSeparator from FileSystem.h and FileSystem.cpp, unless a directly linked coding requirement establishes its need. |
✅ Passed checks (3 passed)
-
Check name Status Explanation Linked Issues check ✅ Passed The change satisfies issue #3100. Both fallback paths inMapCache::addMapnow callgetFileName.getFileNameaccepts/and\\and returns the complete input when no separator exists. This prev…Title check ✅ Passed The title clearly identifies the primary bug fix: handling map names when the path has no separator. It is concise and relevant to the changeset. Description check ✅ Passed The description accurately explains the fallback-name bug, the use of getFileName, supported separators, affected paths, limitations, and verification status.
Full details: Out of Scope Changes check
-
Explanation
The new public
FileSystem::appendPathSeparatordeclaration and implementation are not used by either fallback path and do not support theMapCache::addMapfix for issue#3100. The relatedisPathInDirectoryupdate andPathUtilhelper changes support the path-separator refactor, but this new API has no demonstrated connection to the linked issue.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
289154b to
458f7e1
Compare
458f7e1 to
4fc5be9
Compare
Closes #3100.
Depends on #3105; its commits are included until it merges.
Both fallback display-name paths in
MapCache::addMappreviously added one to the result of a backslash search without checking whether a separator was found. A filename containing only forward slashes, or no separator, could therefore pass an invalid pointer toAsciiString::set.Both paths now use
getFileNamefromLib/PathUtil.h, sharing the separator handling introduced by #3105. It accepts either separator and returns the whole filename when neither is present. The extension is preserved, matching the previous behavior for backslash-separated paths:All changes are in Core.
Verification
git diff --checkpasses.loadMapsFromDiskstill rejects slash-only filenames before reachingaddMap. End-to-end non-Windows scanning also requires the separate map-cache path changes in bugfix(map): Fix map cache paths on non-Windows #3107.