Fix minor bug

v2.1.7

Update CategorisedMocks.swift

Fix minor bug

v1.2.12

chore: Remove a print command

Quick Access, UX improvement 🎉🎉

Introduces a new feature, as a UX improvement,
now LetSee shows the mocks for the last intercepted request just on the screen so there is no need to open the panel and pass the default path to manually select the mock, all mocks for the intercepted request will be shown on the screen near the LetSee button and we can select the mock easily

LetSee.Quick.Acceess.mov

Lets Customize LetSee 🎉🎉

We made it public, all the protocols can be implemented to customize LetSee

struct JsonFileParser: FileNameParsing {
   func parse(_ filePath: FileInformation) throws -> MockFileInformation {
       let fileName = filePath.name.hasSuffix(".json") ? String(filePath.name.dropLast(5)) : filePath.name
       let type: MockFileInformation.MockStatus = fileName.hasPrefix("error_") ? .failure : .success
       let fileInformation = MockFileInformation(fileInformation: filePath,
                                                 statusCode: nil,
                                                 delay: nil,
                                                 status: type,
                                                 displayName: fileName)
       return fileInformation
   }
}

// injects LetSee, this object will be replaced by the default implementation. 
// no need to store this object, LetSee will keep it strongly itself and it is accessible by LetSee.shared
let letSee = LetSee(jsonFileParser: JsonFileParser())
LetSee.injectLetSee(letSee)

🎉🎉🎊🎊 Release Version 1.0.0 🎉🎉🎊🎊

🎉🎉🎊🎊 All the necessary features are up and running

• Easy to use, LetSee receives a folder of your JSON mock data and lets you select them on the runtime
• Scenarios, sometimes you know what the scenario is and you don't want to mock each request manually, you provide a folder of your Scenarios and LetSee lets you select a scenario on the fly
• On the fly response, you are testing your application and suddenly some wired edge case comes to your mind, in this situation you can provide a totally custom JSON as the response to the request
• Live To Server, sometimes you don't want to mock all the requests but only some, in this case, you always have the option to do the actual request to the server instead of providing the mock response for those requests that you don't want to mock
• Copy and Past, you can copy a JSON and past it as the response to the request
• Live Scenario Tracking, If a scenario is activated, you can see the active scenario and the next response that will be passed to the next request
• Change the Scenario On The Fly, you can change the active scenario anytime you like without rerunning the application.