WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
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: packages/telefunc.com/pages/event-based/+Page.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
import { Link } from'@brillout/docpress'
2
2
3
-
> **What is this page about?**
3
+
> **What is this about?**
4
4
>
5
5
> This page explains how to most efficiently use Telefunc (and RPC in general) to significantly increase development speed.
6
6
>
@@ -18,21 +18,21 @@ With Telefunc, it's usually the opposite — telefunctions are:
18
18
19
19
This inversion is at the cornerstone of using Telefunc efficiently.
20
20
21
-
You may be tempted to create generic telefunctions out of habit from REST/GraphQL (or to keep things [DRY](https://softwareengineering.stackexchange.com/questions/400183/what-should-i-consider-when-the-dry-and-kiss-principles-are-incompatible)) but we recommend against it. Instead, we recommend implementing what we call *event-based telefunctions*.
21
+
You may be tempted to create generic telefunctions but we recommend against it. Instead, we recommend implementing what we call *event-based telefunctions*.
0 commit comments