Spelling #802
No reviewers
Labels
No Label
DBF
Dates
Defined Names
Features
Formula
HTML
Images
Infrastructure
Integration
International
ODS
Operations
Performance
PivotTables
Pro
Protection
Read Bug
SSF
SYLK
Style
Write Bug
good first issue
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sheetjs/sheetjs#802
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "spelling"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
You can of course drop commits.
The filename change is a bit odd -> SheetJS/jxls#2 (someone would have to fix this repo once that PR is taken, if it is).
The password change is because it's an annoying false positive. afaict, there's no particular requirement to misspell the word by omitting a character, and thus it's nicer for spelling tools if you just append a suffix which should also result in a non-matching password. There's also a family of tokens such as
C4tegory
.Thanks for looking into this!
The
dynamic
error corresponds to a test file with that name (it's pulled from the jXLS project test suite ), so that should be preserved.Instead of
passwor_
, change the password topasswords
orPassword
orPASSWORD
(pick your favorite).Other weird names like
C4tegory
appear in the test script as fake names for the various properties. The pertinent test starts from the JS representation, writes files, reads the new files, and verifies that the properties of the new file match the original representation. The object's keys should not be changed, but the values can be changed. Feel free to pick your favorite sesquipedalians!Please undo the commit corresponding to
dynamic
, changepasswor
, and squash down to one commit with the messagespelling [ci skip]
(the[ci skip]
part will skip travis tests)The other changes in #803 look good, if you can fold those changes from #803 into this PR with one commit, we can merge as-is! (normally we would do some git jujutsu but GH doesn't recognize a commit as a successful merge unless it has the same exact hash :/
Make the message for the combined commit:
(GH will automatically add a note in both PRs linking to the commit)