Skip to content
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.

Commit

Permalink
docs: add funding + update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
aaimio committed May 29, 2022
1 parent e038374 commit 0c39420
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
1 change: 1 addition & 0 deletions FUNDING.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
github: [aaimio]
4 changes: 2 additions & 2 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -294,7 +294,7 @@ A real life scenario could be to gather a bunch of JSS styles that are generated
**Notes**

- You are **not** required to pass a function as the `<Magic>` component's children, but they allow you to execute functions. Passing regular children (i.e. React elements) will work fine.
- If you return another `<Magic>` component within a child render function of another `<Magic>` component, the priority number will only count for that level of `<Magic>` components. You normally wouldn't run into this scenario.
- If you return another `<Magic>` component within a child render function of another `<Magic>` component, the priority number will only count for that level of `<Magic>` components (think JavaScript event loop). You normally wouldn't run into this scenario.

**Hoisting a component / setting outerHTML**

Expand Down Expand Up @@ -385,7 +385,7 @@ const MyComponent: FunctionComponent<{}> = () => {
></amp-img>
```

You could even write an abstraction over the `<Custom>` component to provide better type hinting for the next person consuming your component. For example:
You could write an abstraction over the `<Custom>` component to provide better type hinting for the next person consuming your component. For example:

```TS
import { Custom } from 'logicful-templates';
Expand Down

0 comments on commit 0c39420

Please sign in to comment.