Bug Description After forking the project and cloning, I am creating a branch. And then it's not building and throwing an error : "Command PhaseScriptExecution failed with a nonzero exit code". The same error is throwing after just cloning the main project without forking it.

Things I have tried

• I did cleaned build
• I did restart the mac
• I re-forked and re-cloned, but still

Mac :- Big Sur 11.4 - Non-M1 Xcode :- 13

I don't think it's only happening on my device??

Requirement

Create a Progress Stepper View, that progress as the user goes through the input Views.

You need to create a UI that starts from the initial state, and you have to increase the step based on user Input.

Proposed Solution

• Create an Observable Object that contains the number of steps and the current step.
• Create Views and pass the Observable Object to it.
• The Stepper view should take the number of steps from the Observable object class and populate the steps.

Bonus Points

• Add animations to the color and style change of the steps as it progress.
• You can create simple next and previous buttons that increases the current step.

Requirements

Add a new markdown (.md) file to the documentation folder that lists all contributors within the project. Consider the optimum style, ideally, the page should contain:

• Information about the project
• List the user's name (linking to their Github - use placeholders for now)
• Contain information about how users can get involved in the project

Anexisting template exists for this, though a table might be better suited.

| Contributor | Position | Social links | |-------------|----------|-------------------| | Name one | ✨ | Twitter Instagram | | Name two | 📖 | Twitter | | Name three | 💻 | Twitter Instagram |

Solution

1. Create file
2. Create sections
3. Populate sections

Is your feature request related to a problem? Please describe. Haptics engages people’s sense of touch to enhance the experience of interacting with onscreen interfaces. This provides feedback when a user taps on a button or an action has been successfully completed.

Describe the solution you'd like Create a class to handle haptic feedback, a singleton object can be used. This will be later used across the app.

A few cases worth handling:

• Heavy
• Light
• Medium
• Rigid
• Error
• Success
• Warning

Please test this, a follow-up issue will be to add feedback to various buttons and actions - though this has not been scoped.

Additional context

• Haptic feedback

This issue is blocked by #8 #3. There is an outstanding issue #9 for the onboarding button - though a placeholder button can be used

Requirements

The UI will need to be created for the onboarding views. This will involve using the Figma design files to layout the images, text, and buttons.

The UI consists of three views:

• Welcome onboarding view - this consists of information regarding the app
• Configure notification onboarding View - allows user to set up notifications
• Goal setting onboarding View - lets a user create a new goal

The functionality of the onboarding such as notifications and creating new goals/habits will be added once the UI has been completed.

Solution

• Welcome onboarding view - image, text & button
• Configure notification onboarding View - image, text & buttons
• Goal setting onboarding View - image, grid, buttons & text

Consider using adaptive columns - https://www.hackingwithswift.com/quick-start/swiftui/how-to-position-views-in-a-grid-using-lazyvgrid-and-lazyhgrid

Requirement

We need an Image View struct that takes in an image, is scalable based on the frame provided by the Parent View. Display a circular image with a border around the image.

Proposed solution

Create a generic Image View Struct under Code > Support Views.

Add variables that takes in an imageName, lineWidth and borderColor.

The View that you should create should look something similar to this-

Once you're done raise a PR. Good luck :)

I have created the onboarding screen as mentioned in #10 However, I am looking for a better way to write those tags group on 3rd onboarding screen. Third screen is not looking arranged because of not having a proper tags arrangement.

Things I did in this pull request:

• Created a view in file -> view -> onboarding
• Created an enum to manage the onboarding screens

[RL] [ADD] onboarding button modifier possibility to change max level of onboarding steps if user will tap on button, the current status will be updated and updates the trim level of black border. [\RL]

Requirement

The onboarding UI contains a button. The button is square and has an outer ring to inform users of how far they are within the onboarding flow. This button will need to be created as a reusable view so that it can be used across all three onboarding views.

Please refer to the Figma file for additional details.

Proposed Solution

SwiftUI does not contain a built-in square. Nonetheless, a rounded rectangle could be used instead and the frame height and width could be modified.

• Create shape using a ZStack
• Create three rectangles - middle, and two outer
• The Second rectangle should be gray
• The third rectangle should be black
• Create two variables of type CGFloat for the position from and to - these will be used to update the black outer ring
• Add system image for the Chevron - which can be found in SFSymbols titled chevron.right

Created the Contributing.md and populated the general guidelines. These guidelines include: branch policy, pull requests, and issue resolution.

Tags were also added to the project to enhance project findability.

Created onboarding views, which only visible on first launch. Can add n views in onboarding, user can skip as well. Each onboarding screen can show a image, heading and description.

Habit tracking needs to persist the data for tracking the habits, so I added the CoreData (Created a Habit Model, which is right now incomplete). As app didn't had any plan for UI Structure, I created 2 tabs i.e., Habits & Analytics. Habits: This tab will be used for tracking, adding new, editing & deleting existing Habits.

Analytics: This tab will show analytics like longest streaks, shortest streak, will try to motivate users by gamifying it.

Using SF Symbols for icons.

Requirements

The current contributing.md file is only half completed.

The Code Structuring section needs to be populated.

Solution

Download the project and review the file structure. Afterward, populate the following sections within Coding Structuring using best practices:

1. Constants & Extensions
2. Comments (functional & explanatory)

You can leave out the code styling section - as I will tackle this at a later stage. Please use code examples where necessary.