Skip to content

Conversation

@OyinloluB
Copy link
Contributor

Why?

Clear and short explanation here.

How?

  • Done A (replace with a breakdown of the steps)
  • Done B
  • Done C

Tickets?

Contribution checklist?

  • The commit messages are detailed
  • It does not break existing features (unless required)
  • I have performed a self-review of my own code
  • Documentation has been updated to reflect the changes
  • Tests have been added or updated to reflect the changes
  • All code formatting pass
  • All lints pass

Security checklist?

  • Injection has been prevented (parameterized queries, no eval or system calls)
  • The UI is escaping output (to prevent XSS)
  • Sensitive data has been identified and is being protected properly

Demo?

Optionally, provide any screenshot, gif or small video.

@OyinloluB OyinloluB self-assigned this Aug 15, 2022
mobileTableHeader: '#FBFBFB',
mobileBackgroundColor: '#FAFAFA',
lightGreyColor: '#3535354d',
navText: '#434D56'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Colours should be named per colour for reusability, not functionality.

* feat: 🎸 connect canister id

* feat: 🎸 modified color name

* refactor: 🎸 wrapped text in translate component
* feat: 🎸 set up collection details section

* feat: 🎸 set up detail forms

* feat: 🎸 set/cleaned up form sections

* feat: 🎸 set up error handling + modal

* remove yarn.lock file
* feat: 🎸 set up onboarding properties/traits

* style: 💅🏼 style updates
* feat: 🎸 set up onboarding properties/traits

* style: 💅🏼 style updates

* feat: 🎸 updated properties section

* refactor: 💡 made some style updates

* feat: 🎸 add new category feature

* refactor: 💡 removed comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants