djorkaeffalexandre / chuck-norris-facts Goto Github PK

• Store Facts Categories on Local Database
• Sync Facts Categories each time the app opens
• Read Categories from Database
• List Facts Categories on SearchFacts View

• Getting Started
  • How to build the app
  • How to execute the app
• All CLI commands
• Screenshots
• Requirements
• Dependencies
• Architecture Briefing

• Generate iOS App icon asset from (iPhone/iPad)
  • https://drive.google.com/file/d/1MNg01wuswX8dcrxwq8iKi1cxVqlBl-wi/view?usp=sharing
• Set the app icon

• Create a Stub of Facts Request
• Create a Facts List scene
• Create a Cell to a Fact
• Show a warning if the list is empty

• Match only the challenge requirements
• Remove store facts logic
• Remove related tests

• Create extensions to prevent duplicate code
• Refactor complex transform operations

• Store past searches
• List past searches
• Order past searches by most recent

• Mock storage
• Reset app data
• UI Testing

• Create a Search Facts scene
• Create a Networking Layer
• Request Facts by query (https://api.chucknorris.io/)
• List Facts

Depends on #8.

• Remove Moya dependency
• Rewrite Moya layer as an own networking layer

• Remove references to Storyboard
• Define folder structures
• Create the base coordinator

• Add SwiftGen
• Add Run Script of SwiftGen
• Add SwiftGen to Documentation
• Localize all app strings

• Store searched facts on local database
• List 10 random facts from database when searchTerm is empty
• Store Fact Categories
• Show Fact Categories

• Merge develop into main
• Set main as default branch
• Create github release

• Install SwiftLint
• Configure SwiftLint
  • Disable name rule
• SwiftLint running on CI

• Use NSLayoutConstraint
• Make classes final as possible
• Improve Category View
• Improve searchFactsDataSource as possible
• Refactor error handling
• Refactor retry

• Networking error
• SyncCategories error
• SearchFacts error
• No Internet error
• Retry sync/search

• Fastlane
  • Tests
  • Delivery
• Github Actions

• Follow a test naming convention
  E.g.: https://www.appsdeveloperblog.com/naming-ios-unit-test-methods/
• Write more tests to Error flows
• Improve testability as possible