Exporting a trigger on OSX in 3.0 previews only adds two .xml suffixes
Bug #1417234 reported by
Vadim Peretokin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mudlet |
Fix Released
|
Low
|
Stephen Lyons | ||
Bug Description
On OSX only and only in 3.0 previews, not in 2.1, exporting a trigger and just giving it a name of "test" will actually create a file test.xml.xml on disk.
Revision history for this message
| Stephen Lyons (slysven) wrote | #1 |
| Changed in mudlet: | |
| assignee: | nobody → Stephen Lyons (slysven) |
Revision history for this message
| Stephen Lyons (slysven) wrote | #2 |
| Changed in mudlet: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Stephen Lyons (slysven) wrote | #3 |
| Changed in mudlet: | |
| status: | In Progress → Fix Committed |
| Changed in mudlet: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Whilst learning about using Travis on our Github repos I read that the MacOs Filesystem is case insensitive - that being the case I bet we have a test for if the filename given by the user ends in ".xml" and then putting that on if it is NOT detected AND the test we use IS CASE SENSITIVE and is not detecting that the given name ending in ".XML" is still a valid one.
I will go and check for the test used - and have a hunt for anything else that might be affected by this...!