docs: LavishScript string comparisons are case-insensitive (not case-sensitive)#1
Open
Kannkor wants to merge 1 commit into
Open
docs: LavishScript string comparisons are case-insensitive (not case-sensitive)#1Kannkor wants to merge 1 commit into
Kannkor wants to merge 1 commit into
Conversation
…he guide) The guide described LavishScript string comparisons as case-sensitive. In practice .Equal / .NotEqual / .Find / .Compare are case-INsensitive; the case-sensitive variants are .EqualCS / .NotEqualCS / .CompareCS (there is no .FindCS). Corrected across the guide. Also clarifies that ExactName-style string-parameter lookups (e.g. Inventory[ExactName,...]) are a separate, genuinely case-sensitive mechanism - not a .Equal comparison - so the two are no longer conflated. Files: 00_MASTER_GUIDE, 01_LavishScript_Fundamentals, 01b_LavishScript_Reference, 02_Quick_Start_Guide, 20_Debugging_And_Troubleshooting. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
The guide described LavishScript string comparisons as case-sensitive. In practice
.Equal/.NotEqual/.Find/.Compareare case-insensitive; the case-sensitive variants are.EqualCS/.NotEqualCS/.CompareCS(there is no.FindCS). This corrects that across the guide.It also clarifies that
ExactName-style string-parameter lookups (e.g.Inventory[ExactName,...]) are a separate, genuinely case-sensitive mechanism -- not a.Equalcomparison -- so the two are no longer conflated.Verified against live ISXEQ2 behaviour.
Files: