📝 DESCRIPTION:

This component is a cell to compose Home View, inside this must be to contain AsyncImage and Texts to show a couple informations about short next launch.

OBS: This class must be refactored when previous PR opened were merged to use patterns create  

🔗 ASSOCIATED DOCUMENTATION: 

Task CARD Figma Prototype

📈 UNIT TESTS:

There was some change?

• [x] NO
• [ ] YES, which?:

There was some addition?

• [x] NO
• [ ] YES, which?: 

📦 DEPENDENCY:

Some dependencies are added ?

• [x] NO 
• [ ] YES, which?:  

Some dependencies are changed ?

• [x] NO 
• [ ] YES, which?:    

📣 ACCESSIBILITY

Has there been any change in accessibility ?

• [x] NO
• [ ] YES, which?: 

Add some accessibility feature ?

• [x] NO
• [ ] YES, which?: 

🖼 EVIDENCY

📍 HOW TO TEST:

FLUX: BUILD APP VARIABLES: At moment does not possible to test, because It's needs to implement at HomeView BRANCH: paolo/feature/NextLaunchView

☑️ CHECK LIST DEV:

• [x] Have I revised the code?
• [x] Am I up to date with develop?
• [x] Removed the prints?
• [x] Does my code follow the style of the project?
• [x] Didn't my changes generate warnings?
• [x] Have my layouts been validated on smaller screens?
• [x] Have my layouts been validated on larger screens?
• [x] I didn't add duplicate code!
• [x] Does not contain loose numbers (magic numbers) 
• [x] Does not contain loose texts 
• [x] Respects the naming standard
• [x] I didn't leave any callbacks with strong references!
• [x] I didn't add 'Force unwrap' (!)
• [x] Is the code following the default language defined for project development?
• [x] The tests are covering >= 70% (if not possible now you can ckecked)
• [ ] My code was reviewed by at least 2 developers

Description of the new feature

Create a empty view for project and a ContentView to separate and componentize and be used throughout the project.

Checklist:

Put an x in the boxes that apply:

• [x] Doesn't add duplicate code
• [x] Doesn't add duplicate code
• [x] Doesnt contain WIP code

Evidence:

| iPhone 12 |

| |

📝 DESCRIPTION:

• Refactored
• Fix Unit test
• add @MainActor
• Create custom cell

🔗 ASSOCIATED DOCUMENTATION: 

Task Notion Figma Prototype

📈 UNIT TESTS:

There was some change?

• [ ] NO
• [x] YES, which?:

• Refactor tests for @MainActor

There was some addition?

• [x] NO
• [ ] YES, which?: 

📦 DEPENDENCY:

Some dependencies are added ?

• [x] NO 
• [ ] YES, which?:  

Some dependencies are changed ?

• [x] NO 
• [ ] YES, which?:    

📣 ACCESSIBILITY

Has there been any change in accessibility ?

• [x] NO
• [ ] YES, which?: 

Add some accessibility feature ?

• [x] NO
• [ ] YES, which?: 

🖼 EVIDENCY

• [ ] NO
• [x] YES, check below:

📍 HOW TO TEST:

FLUX: BUILD APP BRANCH: paolo/feature/LaunchCellView

☑️ CHECK LIST DEV:

• [x] Have I revised the code?
• [x] Am I up to date with develop?
• [x] Removed the prints?
• [x] Does my code follow the style of the project?
• [x] Didn't my changes generate warnings?
• [x] Have my layouts been validated on smaller screens?
• [x] Have my layouts been validated on larger screens?
• [x] I didn't add duplicate code!
• [x] Does not contain loose numbers (magic numbers) 
• [x] Does not contain loose texts 
• [x] Respects the naming standard
• [x] I didn't leave any callbacks with strong references!
• [x] I didn't add 'Force unwrap' (!)
• [x] Is the code following the default language defined for project development?
• [x] The tests are covering >= 70% 
• [ ] My code was reviewed by someone else

📝 DESCRIPTION:

• Refactored
• Create tests for viewModel
• add NextLaunchViewCell on HomeView
• Make class helper to decode json

🔗 ASSOCIATED DOCUMENTATION: 

Figma Prototype

📈 UNIT TESTS:

There was some change?

• [x] NO
• [ ] YES, which?:

There was some addition?

• [ ] NO
• [x] YES, which?: 

• Make HomeViewModelTests
• Make Service Mock to test
• Make Reponse Mock

📦 DEPENDENCY:

Some dependencies are added ?

• [x] NO 
• [ ] YES, which?:  

Some dependencies are changed ?

• [x] NO 
• [ ] YES, which?:    

📣 ACCESSIBILITY

Has there been any change in accessibility ?

• [x] NO
• [ ] YES, which?: 

Add some accessibility feature ?

• [x] NO
• [ ] YES, which?: 

🖼 EVIDENCY

• [ ] NO
• [x] YES, check below:

📍 HOW TO TEST:

FLUX: BUILD APP BRANCH: paolo/feature/HomeViewComplete

☑️ CHECK LIST DEV:

• [x] Have I revised the code?
• [x] Am I up to date with develop?
• [x] Removed the prints?
• [x] Does my code follow the style of the project?
• [x] Didn't my changes generate warnings?
• [x] Have my layouts been validated on smaller screens?
• [x] Have my layouts been validated on larger screens?
• [x] I didn't add duplicate code!
• [x] Does not contain loose numbers (magic numbers) 
• [x] Does not contain loose texts 
• [x] Respects the naming standard
• [x] I didn't leave any callbacks with strong references!
• [x] I didn't add 'Force unwrap' (!)
• [x] Is the code following the default language defined for project development?
• [x] The tests are covering >= 70% 
• [ ] My code was reviewed by someone else

📝 DESCRIPTION:

• Add Service calls in ViewModel
• Add Published properties in ViewModel to notify View
• Add Add ViewModel as StateObject  

🔗 ASSOCIATED DOCUMENTATION: 

Figma Prototype

📈 UNIT TESTS:

There was some change?

• [x] NO
• [ ] YES, which?:

There was some addition?

• [x] NO
• [ ] YES, which?: 

📦 DEPENDENCY:

Some dependencies are added ?

• [x] NO 
• [ ] YES, which?:  

Some dependencies are changed ?

• [x] NO 
• [ ] YES, which?:    

📣 ACCESSIBILITY

Has there been any change in accessibility ?

• [x] NO
• [ ] YES, which?: 

Add some accessibility feature ?

• [x] NO
• [ ] YES, which?: 

🖼 EVIDENCY

• [x] NO
• [ ] YES, check below:

📍 HOW TO TEST:

FLUX: BUILD APP VARIABLES: At moment does not possible to test, because It's needs to implement at HomeView or LaunchView BRANCH: paolo/feature/nextLaunchAPI

☑️ CHECK LIST DEV:

• [x] Have I revised the code?
• [x] Am I up to date with develop?
• [x] Removed the prints?
• [x] Does my code follow the style of the project?
• [x] Didn't my changes generate warnings?
• [x] Have my layouts been validated on smaller screens?
• [x] Have my layouts been validated on larger screens?
• [x] I didn't add duplicate code!
• [x] Does not contain loose numbers (magic numbers) 
• [x] Does not contain loose texts 
• [x] Respects the naming standard
• [x] I didn't leave any callbacks with strong references!
• [x] I didn't add 'Force unwrap' (!)
• [x] Is the code following the default language defined for project development?
• [x] The tests are covering >= 70% (if not possible now you can ckecked)
• [ ] My code was reviewed by at least 2 developers

📝 DESCRIPTION:

• Refactored SpaceXAPI to become easier to use in future
• Create a Endpoint protocol
• Create Classes that inherit Endpoint to pass inside generic method
• Create generic methods
• Refactor old fetchAllLaunchs methods
• Create new method named fetchNextLaunch  

🔗 ASSOCIATED DOCUMENTATION: 

Task CARD Figma Prototype Artigo that was read to implement async returns

📈 UNIT TESTS:

There was some change?

• [x] NO
• [ ] YES, which?:

There was some addition?

• [x] NO
• [ ] YES, which?: 

📦 DEPENDENCY:

Some dependencies are added ?

• [x] NO 
• [ ] YES, which?:  

Some dependencies are changed ?

• [x] NO 
• [ ] YES, which?:    

📣 ACCESSIBILITY

Has there been any change in accessibility ?

• [x] NO
• [ ] YES, which?: 

Add some accessibility feature ?

• [x] NO
• [ ] YES, which?: 

🖼 EVIDENCY

• [x] NO
• [ ] YES, check below:

📍 HOW TO TEST:

FLUX: BUILD APP VARIABLES: At moment does not possible to test, because It's needs to implement at HomeView or LaunchView BRANCH: paolo/feature/nextLaunchAPI

☑️ CHECK LIST DEV:

• [x] Have I revised the code?
• [x] Am I up to date with develop?
• [x] Removed the prints?
• [x] Does my code follow the style of the project?
• [x] Didn't my changes generate warnings?
• [x] Have my layouts been validated on smaller screens?
• [x] Have my layouts been validated on larger screens?
• [x] I didn't add duplicate code!
• [x] Does not contain loose numbers (magic numbers) 
• [x] Does not contain loose texts 
• [x] Respects the naming standard
• [x] I didn't leave any callbacks with strong references!
• [x] I didn't add 'Force unwrap' (!)
• [x] Is the code following the default language defined for project development?
• [x] The tests are covering >= 70% (if not possible now you can ckecked)
• [ ] My code was reviewed by at least 2 developers

Description

• Added LaunchCellView component
• Added Color extension to accept hex strings
• Decrease iOS target to 15.0

Checklist:

• [X] Does not add duplicated code
• [X] Does not contain commented code
• [ ] Does not contain WIP code (Need to improve colors and fontSize constants)

Evidences:

📝 DESCRIPTION:

In this branch I create a custom TabBar named SPTabBar, for this I Needed to create a custom TabBarIcons, trying to follow atomic design. For this task I preferred to create a helper style implemented in some companies to make more easier custom methods and properties with extensions. Create a Constant files to avoid magic numbers and strings.  

🔗 ASSOCIATED DOCUMENTATION: 

Task CARD Figma Prototype

📈 UNIT TESTS:

There was some change?

• [x] NO
• [ ] YES, which?:

There was some addition?

• [x] NO
• [ ] YES, which?: 

📦 DEPENDENCY:

Some dependency are added ?

• [x] NO 
• [ ] YES, which?:  

Some dependency are changed ?

• [x] NO 
• [ ] YES, which?:    

📣 ACCESSIBILITY

Has there been any change in accessibility ?

• [x] NO
• [ ] YES, which?: 

Add some accessibility feature ?

• [x] NO
• [ ] YES, which?: 

🖼 EVIDENCY

📍 HOW TO TEST:

FLUX: BUILD APP VARIABLES: Does not have variables. BRANCH: paolo/feature/tabBar  

☑️ CHECK LIST DEV:

• [x] Have I revised the code?
• [x] Am I up to date with develop?
• [x] Removed the prints?
• [x] Does my code follow the style of the project?
• [x] Didn't my changes generate warnings?
• [x] Have my layouts been validated on smaller screens?
• [x] Have my layouts been validated on larger screens?
• [x] I didn't add duplicate code!
• [x] Does not contain loose numbers (magic numbers) 
• [x] Does not contain loose texts 
• [x] Respects the naming standard
• [x] I didn't leave any callbacks with strong references!
• [x] I didn't add 'Force unwrap' (!)
• [x] Is the code following the default language defined for project development?
• [x] The tests are covering >= 70% (if not possible now you can ckecked)
• [ ] My code was reviewed by at least 2 developers

• What does this PR do
 - Was implemented a ErrorView to be returned when the network requests fails.

• TODOs
 - Turn off the network connection and confirm if in the Lauches tab, the scene will be replaced by the ErrorView.

• ANY BACKGROUND CONTEXT YOU WANT TO PROVIDE
 - Nops

What changed?

Create a Network layer to handle with network on the application and create a service for integrating launches endpoint.

Why?

These will increase integration between other APIs on application.

How?

Create our own NetworkManager and a Service layer to handle integration for launches service.

Screenshots

No need.

Description of the new feature

Create a new header for LaunchDetailsView, and some changes for add new inputs on Design System.

p.s: sorry about this image lol

Checklist:

Put an x in the boxes that apply:

• [x] Doesn't add duplicate code
• [x] Doesn't add duplicate code
• [x] Doesnt contain WIP code

Evidence:

| iPhone 12 |

| |