Optional side property for examples

Added an optional side property, which allows specifying the type of the example on pages other than function definitions, where the type is determined automatically. An example would be element pages like Vector2, where the type can't be detected automatically and manual specification is useful.

Author: FileEX

elements/Matrix/Matrix.yaml

@@ -106,9 +106,12 @@ examples:
   - path: examples/matrix-1.lua
     description: >
       Say you wanted to create a bin - object 1337 - two units in front of a player. You don't want to manually do trigonometry and you don't want to play with the complicated tables. You just want to get the position two units in front of the player whilst taking into account the rotation of the player. You only need to use Matrix.getForward, Matrix.getPosition and getElementMatrix. It's just:
+    side: 'shared'
   - path: examples/matrix-2.lua
     description: >
       If you wanted the opposite of matrix.forward you'll still use matrix.forward but you minus it instead of matrix.backward which doesn't exist. Same applies with matrix.right and matrix.up. To make the bin object appear behind a player:
+    side: 'shared'
   - path: examples/matrix-3.lua
     description: >
-      Say you'd like to get find the position underneath a vehicle. This is the position at any rotation. So if it was upside down, the Z value would be higher than the vehicle Z value. If the vehicle was the right way round, the Z value for underneath car would be less than the Z value for the car.
+      Say you'd like to get find the position underneath a vehicle. This is the position at any rotation. So if it was upside down, the Z value would be higher than the vehicle Z value. If the vehicle was the right way round, the Z value for underneath car would be less than the Z value for the car.
+    side: 'shared'

elements/Vector/Vector2.yaml

@@ -99,5 +99,7 @@ oop_only_methods:
 examples:
   - path: examples/vector2-1.lua
     description: Checks if the player is using a low resolution
+    side: 'client'
   - path: examples/vector2-2.lua
-    description: Draws a red line from center to cursor, 200px long
+    description: Draws a red line from center to cursor, 200px long
+    side: 'client'

elements/Vector/Vector3.yaml

@@ -183,13 +183,18 @@ oop_only_methods:
 examples:
   - path: examples/vector3-1.lua
     description: This example sorts all players in a nice line on the center of the map.
+    side: 'shared'
   - path: examples/vector3-2.lua
     description: >
       This example creates a tiny sun which is always at the right of the vehicle the local player drives. By default it will draw the vectors used to compute the position where it should be, so you can understand what does this function do. Note that the code could be made simpler by simply getting the right component of the vehicle matrix. Make sure that you put this code in a resource which has OOP enabled, or it won't work.
+    side: 'client'
   - path: examples/vector3-3.lua
     description: >
       This examples illustrates the concept of dot/scalar product and implements a useful function which can be used to get the angle between two vectors. 
+    side: 'shared'
   - path: examples/vector3-4.lua
     description: This example slowly moves all the players' camera to look at the Mount Chilliad.
+    side: 'client'
   - path: examples/vector3-5.lua
     description: This example slowly moves all the players' camera to look at the Mount Chilliad with a shorter code than the previous example.
+    side: 'client'

elements/Vector/Vector4.yaml

@@ -26,4 +26,5 @@ oop_only_methods:
 
 examples:
   - path: examples/vector4-1.lua
-    description: This example adds a command called "/garage", allowing you to get any garage bounding box. 
+    description: This example adds a command called "/garage", allowing you to get any garage bounding box. 
+    side: 'client'

schemas/common-defs.yaml

@@ -120,6 +120,9 @@ $defs:
         exampleTitle:
           type: string
           description: Optional title displayed in the frame around the example.
+        side:
+          type: string
+          description: Optionally, you can specify the type of the example. In the case of function definitions, the type is automatically determined based on the client, server, or shared section.
 
   see_also:
     type: array