Fix class file name casing for Linux compatibility#27
Open
dbeja wants to merge 1 commit into
Open
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
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.
Fixes #26.
Description
This PR updates the filename
class-quickal.phptoclass-QuickAL.phpto match the class name QuickAL and ensure compatibility with case-sensitive filesystems (e.g. most Linux servers).Issue
On Linux, the autoloader was failing because it was looking for class-QuickAL.php (based on the class name QuickAL), but the actual file was named class-quickal.php. This worked locally on macOS (which has a case-insensitive filesystem by default) but caused fatal errors in production.
Issue reported on #25 by @jrgong420.
Solution
Renamed the file using git mv to preserve version history and ensure Git tracks the change in casing.
Why this approach