@ -18,7 +18,7 @@ Put yourself in their position, and imagine how they would feel about your featu
|
|||||||
|
|
||||||
1. Is it easy to use?
|
1. Is it easy to use?
|
||||||
2. Has it been documented well?
|
2. Has it been documented well?
|
||||||
3. Is it intuative?
|
3. Is it intuitive?
|
||||||
4. Is it consistent with the rest of the API?
|
4. Is it consistent with the rest of the API?
|
||||||
5. Is it fun to use?
|
5. Is it fun to use?
|
||||||
|
|
||||||
@ -39,7 +39,7 @@ Unesesary coment removed // Make sure to use correct spelling
|
|||||||
|
|
||||||
> This mainly applies to the API the end user will consume.
|
> This mainly applies to the API the end user will consume.
|
||||||
|
|
||||||
Try to make method parameters of the outside API accept primatives, or `json` objects, so that child components are created **inside** the component, rather than being **injected** in.
|
Try to make method parameters of the outside API accept primitives, or `json` objects, so that child components are created **inside** the component, rather than being **injected** in.
|
||||||
|
|
||||||
This is so that:
|
This is so that:
|
||||||
|
|
||||||
@ -65,7 +65,7 @@ This is so that:
|
|||||||
|
|
||||||
**Do**
|
**Do**
|
||||||
|
|
||||||
`ITableFloatOptions` is an interface for a JSON of primatives. The end user would need to pass in a json object and not need to worry about the internals:
|
`ITableFloatOptions` is an interface for a JSON of primitives. The end user would need to pass in a json object and not need to worry about the internals:
|
||||||
|
|
||||||
```js
|
```js
|
||||||
public float(tableFloatOptions: ITableFloatOptions): Table
|
public float(tableFloatOptions: ITableFloatOptions): Table
|
||||||
|
Reference in New Issue
Block a user