Add get_relative_path() to base filesystem methods #96
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.
Feature Description
This PR introduces the get_relative_path function, which computes the relative path from a given base path to a specified file. The function signature is as follows:
Functionality
The get_relative_path function takes two parameters:
The function returns a string representing the relative path from base_path to filename. This is useful in scenarios where relative paths are needed for portability, readability, or other path manipulations.
Usage Examples
Below are some examples demonstrating how to use the get_relative_path function:
Testing
Comprehensive tests have been added to ensure the correctness of the get_relative_path function. The tests cover various scenarios, including:
Related to aseprite/aseprite#4389
I agree that my contributions are licensed under the MIT License.
You can find a copy of this license at https://opensource.org/licenses/MIT