You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-6Lines changed: 2 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,8 +51,6 @@ const breakpoints = {
51
51
};
52
52
```
53
53
54
-
> Tip: Each key in this object will become a prop on your components--watch out for naming conflicts!
55
-
56
54
The values that you provide are the "maximum pixel-widths" for that screen class. In order to make sure that all possible screen pixel-sizes are handled, there should be exactly one screen class with a value of `Infinity` which tells us that there is no maximum pixel-width for that screen class.
57
55
58
56
### 2. Generate your custom Responsive System with `createResponsiveSystem`
@@ -95,8 +93,6 @@ ReactDOM.render(
95
93
96
94
### 4. Make your components responsive
97
95
98
-
#### a. `useResponsiveValue`
99
-
100
96
Now that the app is aware of the current screen class, we can declare values that dynamically change to fit any screen!
101
97
102
98
```js
@@ -221,7 +217,7 @@ Fundamentally, we need our components to be aware of the current screen class so
221
217
222
218
## Changelog
223
219
224
-
Responsive System uses strict Semantic Versioning which means that our version numbers carry extra meaning. Then general form is:
220
+
Responsive System uses strict Semantic Versioning which means that our version numbers carry extra meaning. The general form is:
225
221
226
222
`v{major}.{minor}.{patch}`
227
223
@@ -245,7 +241,7 @@ The reason that we haven't moved to 1.0 yet is that the API just hasn't felt qui
245
241
246
242
So what changed?
247
243
248
-
In 0.9 we moved away from the HOC `responsive(Component)` approach and adopted a streamlined hook-based approach. The hook-based approach is much smaller (in terms of bytes) and much lighter in the sense that we no longer modify your components "magically". Fundamentally, we've shifted from wrapping entire components to make them responsive to wrapping individual values/variables.
244
+
In 0.9 we moved away from the HOC `responsive(Component)` approach and adopted a streamlined hook-based approach. The hook-based approach is much smaller (in terms of bytes) and much lighter in the sense that we no longer modify your components "magically". Fundamentally, we've shifted from wrapping entire components to wrapping individual values/variables.
0 commit comments