Code - Revision history

Zhell at 20:08, 28 April 2023

2023-04-28T20:08:24Z

Zhell at 02:02, 2 April 2023

2023-04-02T02:02:22Z

Zhell at 01:59, 2 April 2023

2023-04-02T01:59:58Z

Zhell at 01:58, 2 April 2023

2023-04-02T01:58:38Z

Zhell at 01:57, 2 April 2023

2023-04-02T01:57:54Z

Zhell at 18:18, 27 March 2023

2023-03-27T18:18:43Z

Zhell at 19:17, 15 December 2022

2022-12-15T19:17:33Z

Zhell at 19:12, 15 December 2022

2022-12-15T19:12:52Z

Zhell at 19:12, 15 December 2022

2022-12-15T19:12:15Z

Zhell at 19:11, 15 December 2022

2022-12-15T19:11:22Z

← Older revision		Revision as of 20:08, 28 April 2023
Line 184:		Line 184:
	Now that you understand the basics of Codes, let's see how to use them to create [[Tokens]]		Now that you understand the basics of Codes, let's see how to use them to create [[Tokens]]

−	[[Category:~~run-doc~~]]	+	[[Category:Documentation]]

@@ Line 18: / Line 18: @@
 Deploy a sidekick function
 function sha256(data) { ... }
@@ Line 23: / Line 24: @@
 await sha256Code.sync()
 == Loading ==
@@ Line 29: / Line 31: @@
 Load a Data class
 const Data = await run.load('<class-location-goes-here>')
 const data = new Data('abc')
 Alternatively, you can use the inventory to find your code. run.inventory.sync() will load all the code that you own and place it in the run.inventory.code array. You can filter that array by origin to find the code you plan to use.
@@ Line 39: / Line 43: @@
 Find a class you own in the inventory
 await run.inventory.sync()
 const MyClass = run.inventory.code.find(C => C.origin === myClassOrigin)
 == Linking ==
@@ Line 51: / Line 57: @@
 Deploy a jig class with a dependency
 class Reward extends Jig { ... }
@@ Line 60: / Line 67: @@
 run.deploy(LootBox)
 == Extending ==
@@ Line 67: / Line 75: @@
 To extend a class, you use the extends keyword as you normally would in JavaScript. When you deploy an extension class, Run will automatically create separate outputs for both the parent and the child and link them together. You do not need to add the parent class to the deps object on the child. Run is smart enough to automatically find the parent.
 class EditablePost extends Post {
    edit(message) {
@@ Line 72: / Line 81: @@
+   }
+}
 Inside methods on the child class, you can call the parent class's methods by using the super keyword in JavaScript. This is useful when you want to override a method on the parent to add behavior but you still want to call the parent method inside.
@@ Line 84: / Line 94: @@
 Load a class at its origin and fast-forward it to its latest state
 const DigitalPet = await run.load('<digital-pet-class-origin>')
 await DigitalPet.sync()
 == Updating ==
@@ Line 96: / Line 109: @@
 You should think of code as living objects with their own history. Although only jig classes can have static methods that update their state, all code including sidekicks can be upgraded, destroyed, and authed.
 class Weapon extends Jig {
    static setPower(power) {
@@ Line 107: / Line 122: @@
 // WeaponCode.power === 100
 == Upgrading ==
@@ Line 128: / Line 144: @@
   Warning: Upgrades cannot be forced onto existing jigs without their owner's permission. If you discover a critical bug, upgrading may not always be an option and you may have to reissue jigs.
 const OldWeapon = await run.load('<weapon-class-location>')
@@ Line 143: / Line 160: @@
 await OldWeapon.sync()
 == Trusting ==
@@ Line 154: / Line 172: @@
 It is also possible to trust all code by passing "*" into run.trust(). This is strongly discouraged for production applications, but it can be useful during development and testing.
 // Trust the class
 run.trust('<your-class-origin-txid>')
@@ Line 159: / Line 178: @@
 // Trust an upgrade
 run.trust('<your-class-upgrade-location-txid>')
 = Where to go from here =

@@ Line 159: / Line 159: @@
 // Trust an upgrade
 run.trust('<your-class-upgrade-location-txid>')
 [[Category:run-doc]]

@@ Line 109: / Line 109: @@
 == Upgrading ==
 == Trusting ==
 [[Category:run-doc]]

@@ Line 9: / Line 9: @@
 == Deploying ==
 == Loading ==
 == Linking ==
 == Extending ==
 == Syncing ==
 == Updating ==
 == Upgrading ==
 == Trusting ==

← Older revision		Revision as of 18:18, 27 March 2023
Line 16:		Line 16:
	== Upgrading ==		== Upgrading ==
	== Trusting ==		== Trusting ==
		+
		+
		+	[[Category:run-doc]]

@@ Line 5: / Line 5: @@
 There are two kinds of Code that Run supports:
 #'''Jig classes:''' Jig classes are classes that extend from Jig and behave like jigs. You already know these. You can use them to create jig objects as we've already seen, but you can also call methods on them to update their properties over time. Jig classes evolve according to same [https://run.network/docs/#how-it-works-ownership-rules Ownership Rules] as jig objects.
-#'''Sidekicks:''' Sidekicks are your helpers. They are your classes or functions that don't extend from <code>Jig</code> which you use more for supporting roles. You might use sidekicks to create a [https://run.network/docs/#advanced-usage-locks custom lock], to define a [https://run.network/docs/#advanced-usage-berries berry], to make a shared helper like [https://run.network/docs/#api-reference-extras-expect expect], or even to store your server code on-chain. When you call a method on a sidekick, nothing gets recorded to Bitcoin. But you can call sidekicks from inside jigs and even from your own app. There are no restrictions on what kinds of parameters can be passed into or returned from sidekicks.
+#'''Sidekicks:''' Sidekicks are your helpers. They are your classes or functions that don't extend from <code>Jig</code> which you use more for supporting roles. You might use sidekicks to create a [https://run.network/docs/#advanced-usage-locks custom lock], to define a [https://run.network/docs/#advanced-usage-berries berry], to make a shared helper like [https://run.network/docs/#api-reference-extras-expect expect], or even to store your server code on-chain. When you call a method on a sidekick, nothing gets recorded to Bitcoin. But you can call sidekicks from inside jigs and even from your own app. There are no restrictions on what kinds of parameters can be passed into or returned from sidekicks. [[Sidekicks|Read more about Sidekicks here.]]
 Using jig classes and sidekicks, you have a powerful repertoire to build extensible apps.

← Older revision		Revision as of 19:12, 15 December 2022
Line 8:		Line 8:
	Using jig classes and sidekicks, you have a powerful repertoire to build extensible apps.		Using jig classes and sidekicks, you have a powerful repertoire to build extensible apps.

−	Deploying~~<br>~~Loading~~<br>~~Linking~~<br>~~Extending~~<br>~~Syncing~~<br>~~Updating~~<br>~~Upgrading~~<br>~~Trusting~~<br>~~	+	== Deploying ==
		+	== Loading ==
		+	== Linking ==
		+	== Extending ==
		+	== Syncing ==
		+	== Updating ==
		+	== Upgrading ==
		+	== Trusting ==