status-im
/
status-react
mirror of https://github.com/status-im/status-react.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update to Quo Readme 

Signed-off-by: Gheorghe Pinzaru <feross95@gmail.com>
This commit is contained in:
Gheorghe Pinzaru 2020-11-08 10:16:00 +03:00
parent 6eb840c8b2
commit 72591f576d
No known key found for this signature in database
GPG Key ID: C9A094959935A952
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
src/quo/README.md
View File

@ -1,13 +1,13 @@
# Status Quo Components # Status Quo Components
All components in **Quo** should be independent of the app state. They should be pure, All components in **Quo** should be independent of the app state. They should be _pure_
and easy to reason about. This is required to make the library independent and and _easy to reason about_. Avoiding the app state is also required to make the library
easily pulled off as a separate repository when needed. independent and easy to be pulled off as a separate repository when needed.
Do avoid high coupling and direct use of internal styling, the components should be To avoid high coupling and direct use of internal styling, the components should be
exported via namespace `quo.core` and used by status app only from here. This will exported via namespace `quo.core` and used by the Status app only from there. This will
allow a more flexible way to update components without possible breakages into the allow a more flexible way to update components without possible breakages into the
app style. app style.
**Quo** components should and not have any dependency on the status app, this **Quo** components should not have any dependency on the Status app, this
will avoid circular dependency and also benefit the independence of the components. will avoid circular dependency and also benefit the independence of the components.
All components are stored inside `components` namespaces. They are stateless and do All components are stored inside `components` namespaces. They are stateless and do
@ -39,8 +39,8 @@ system to be used in too many way which can creating disjointed experiences.
- Avoid external margins for atom components, it can be added on the wrapper - Avoid external margins for atom components, it can be added on the wrapper
where they are used but can't be removed without overriding. where they are used but can't be removed without overriding.
[Max Stoiber article on margins](https://mxstbr.com/thoughts/margin) [Max Stoiber article on margins](https://mxstbr.com/thoughts/margin)
- Design reusable components into [Layout Isolated Components](https://visly.app/blog/layout-isolated-components) - Design reusable components into [Layout Isolated Components](https://visly.app/blogposts/layout-isolated-components)
(Article more relates to web, but ideas fits also to mobile dev** (Article more relates to web, but ideas fits also to mobile development)
- Explicit is better than implicit, do not rely on platform default, if you expect - Explicit is better than implicit, do not rely on platform default, if you expect
a specific value, then override it a specific value, then override it