docs: cleanup

Author: rigor789

content/guide/android-marshalling.md

@@ -19,6 +19,7 @@ There are various ways to manage data flow, often referred to as data bindings:
 ```xml
 <Label text="{{ name }}" />
 ```
+
 ```ts
 export class HelloWorldModel extends Observable {
         name = "John Doe"
@@ -27,14 +28,16 @@ export class HelloWorldModel extends Observable {
 
 }
 ```
+
 - **One-way (to Model) data binding** - Binding which updates the model in relation to some action in the UI. The best example for this is a [tap](/guide/ui-components/gestures-in-nativescript#tap-gesture-in-nativescript) event.
 
 ```xml
 <Button text="Submit" tap="{{ onTap }}"/>
 ```
+
 ```ts
 export class HelloWorldModel extends Observable {
-        
+
         onTap(args: EventData){
 
         }
@@ -49,6 +52,7 @@ export class HelloWorldModel extends Observable {
 ```xml
 <TextField text="{{ name }}"/>
 ```
+
 ```ts
 export class HelloWorldModel extends Observable {
         name = "John Doe"
@@ -60,12 +64,13 @@ export class HelloWorldModel extends Observable {
 
 ## Accessing parent bindingContext
 
-A parent  and a child UI components can have different binding contexts and the child component might need to bind its property to a source property in its parent's **bindingContext**.
+A parent and a child UI components can have different binding contexts and the child component might need to bind its property to a source property in its parent's **bindingContext**.
 
 <!-- TODO: fix links -->
-Generally, the binding context is inheritable, but not when the components are created dynamically based on some data source. For example, [ListView]() creates its child items based on an `itemТemplate`, which describes what the ListView component will look like. When this component is added to the visual tree, for binding context it gets an element from a `ListView` items array (with the corresponding index). 
 
-This process creates a new binding context chain for the child item and its inner UI components. So, the inner UI component cannot access the binding context of the `ListView`. In order to solve this problem, NativeScript binding infrastructure has two special keywords: 
+Generally, the binding context is inheritable, but not when the components are created dynamically based on some data source. For example, [ListView]() creates its child items based on an `itemТemplate`, which describes what the ListView component will look like. When this component is added to the visual tree, for binding context it gets an element from a `ListView` items array (with the corresponding index).
+
+This process creates a new binding context chain for the child item and its inner UI components. So, the inner UI component cannot access the binding context of the `ListView`. In order to solve this problem, NativeScript binding infrastructure has two special keywords:
 
 - `$parent` : denotes the binding context of the direct parent visual component
 - `$parents` : can be used as an array (with a number or string index). This gives you the option to choose either N levels of UI nesting or get a parent UI component with a given type.
@@ -85,22 +90,23 @@ NativeScript supports the following polymorphic binding expressions:
 ### Property access
 
 To access a value stored in an object property of the bindingContext, use the propert access expression:
- 
- ```ts
- ...
- user = {
-  names:{
-      first: "Sara"
-  }
+
+```ts
+...
+user = {
+ names:{
+     first: "Sara"
  }
- ...
- ```
+}
+...
+```
 
- ```xml
+```xml
 
 <Label text="{{  user.name.first  }}" textWrap="true" />
 
 ```
+
 ---
 
 ### array access
@@ -166,23 +172,29 @@ Supported operators: `>`,`<`, `<=`, `>=`, `==`, `!=`, `===`, `!==`.
 <Label text="{{  prop1 ? prop2 : prop3  }}" textWrap="true" />
 
 ```
+
 ---
+
 ### grouping parenthesis
 
 ```xml
 
 <Label text="{{  prop1*(prop2 + prop3)  }}" textWrap="true" />
 
 ```
+
 ---
+
 ### function calls
 
 ```xml
 
 <Label text="{{  someMethod(p1,p2,...,pN)  }}" textWrap="true" />
 
 ```
+
 ---
+
 ### comparison operators
 
 ```xml
@@ -194,6 +206,7 @@ Supported operators: `>`,`<`, `<=`, `>=`, `==`, `!=`, `===`, `!==`.
 Other supported operators are: `<`, `<=`, `>=`, `==`, `!=`, `===`, `!==`.
 
 ---
+
 :::tip Note
 Special characters need to be escaped as follows:
 
@@ -209,17 +222,17 @@ Often data within the Model is stored in a way that is optimized for best perfor
 
  <!-- TODO: Add SB+Preview -->
 
- ```xml
+```xml
 
-  <StackLayout class="p-20 bg">
+ <StackLayout class="p-20 bg">
 
-  <Label text="{{ date | dateConverter('dd-mm-yyyy') }}" textWrap="true" />
-  <Label text="{{ name | toUpperCaseConverter }}" textWrap="true" />
-  <Label text="{{ title | toTitle }}" textWrap="true" />
+ <Label text="{{ date | dateConverter('dd-mm-yyyy') }}" textWrap="true" />
+ <Label text="{{ name | toUpperCaseConverter }}" textWrap="true" />
+ <Label text="{{ title | toTitle }}" textWrap="true" />
 
-  </StackLayout>
+ </StackLayout>
 
- ```
+```
 
 ```ts
 export class HelloWorldModel extends Observable {
@@ -231,7 +244,7 @@ export class HelloWorldModel extends Observable {
   toUpperCaseConverter = this.toUpperCase()
   toTitle = this.convertToTitle()
 
-  ... 
+  ...
 
 formatDate() {
     return {
@@ -274,4 +287,4 @@ Generally there is no need to stop binding explicitly since the Observable objec
 
 ```ts
 targetTextField.unbind('text')
-```
+```

content/guide/data-binding.md

@@ -105,10 +105,9 @@ array.setObjectAtIndex(button, 1)
 
 ## Calling Objective-C/Swift methods with multiple arguments
 
-Consider the following `NSMutableArray` selector: `replaceObjectsInRange:withObjectsFromArray:range:`. 
-
-In JavaScript it is represented by: `replaceObjectsInRangeWithObjectsFromArrayRange(objectsToRange, sourceArray, sourceRange)` (argument names are arbitrary). 
+Consider the following `NSMutableArray` selector: `replaceObjectsInRange:withObjectsFromArray:range:`.
 
+In JavaScript it is represented by: `replaceObjectsInRangeWithObjectsFromArrayRange(objectsToRange, sourceArray, sourceRange)` (argument names are arbitrary).
 
 In Objective-C, when generating the function name for a method, it follows a convention of appending the names of the arguments defined by the Objective-C selector. The function name starts with a lowercase letter for the first argument and appends subsequent arguments with a capital letter.
 
@@ -123,7 +122,8 @@ For an example of how to extend an Objective-C/Swift class, have a look at [Exte
 The below code shows how to convert a JavaScript array to a `CGFloat` array to pass it to an Objective-C method expecting `CGFloat` as an argument:
 
 ```js
-const CGFloatArray = interop.sizeof(interop.types.id) == 4 ? Float32Array : Float64Array
+const CGFloatArray =
+  interop.sizeof(interop.types.id) == 4 ? Float32Array : Float64Array
 const jsArray = [4.5, 0, 1e-5, -1242e10, -4.5, 34, -34, -1e-6]
 
 FloatArraySample.dumpFloats(CGFloatArray.from(jsArray), jsArray.length)
@@ -157,30 +157,31 @@ On the other hand, any API that expects a `NSNull`, `NSNumber`, `NSString` or `N
 ### Converting numeric types
 
 ```ts
-console.log(`pow(2.5, 3) = ${Math.pow(2.5, 3)}`);
+console.log(`pow(2.5, 3) = ${Math.pow(2.5, 3)}`)
 ```
+
 The iOS Runtime converts JavaScript number literals to native doubles and utilizes the native pow(double x, double y) function. The resulting native integer is automatically converted back to a JavaScript number and then passed as an argument to console.log() for output..
 
 ### Converting string
+
 ```ts
-let button = UIButton.new();
-button.setTitleForState('Button title', UIControlState.Normal); 
-console.log(button.titleLabel.text);
+let button = UIButton.new()
+button.setTitleForState('Button title', UIControlState.Normal)
+console.log(button.titleLabel.text)
 ```
 
 `Button title` is converted to `NSString` and the returned `NSString` is converted to JavaScript `string`.
 
 ### Converting boolean
 
 ```ts
-let str = NSString.stringWithString('YES');
-let isTrue = str.boolValue;
+let str = NSString.stringWithString('YES')
+let isTrue = str.boolValue
 ```
 
 ## Objective-C Protocols
 
-Protocols in Objective-C serve a similar purpose as interfaces in other programming languages. They define a blueprint or contract that specifies the members (methods, properties, etc.) that a class should implement.  Protocols are exposed as empty objects in JavaScript. Protocols are usually only referenced when [subclassing](/guide/subclassing/extending-classes-and-conforming-protocols-ios) an Objective-C class or when checking whether an object or class conforms to a protocol.
-
+Protocols in Objective-C serve a similar purpose as interfaces in other programming languages. They define a blueprint or contract that specifies the members (methods, properties, etc.) that a class should implement. Protocols are exposed as empty objects in JavaScript. Protocols are usually only referenced when [subclassing](/guide/subclassing/extending-classes-and-conforming-protocols-ios) an Objective-C class or when checking whether an object or class conforms to a protocol.
 
 ```objc
 BOOL isCopying = [NSArray conformsToProtocol:@protocol(NSCopying)];
@@ -189,6 +190,7 @@ BOOL isCopying = [NSArray conformsToProtocol:@protocol(NSCopying)];
 ```js
 const isCopying = NSArray.conformsToProtocol(NSCopying)
 ```
+
 To implement Objective-C/Swift protocols in NativeScript, hava look at [Conforming to Objective-C/Swift protocols in NativeScript](/guide/subclassing/extending-classes-and-conforming-protocols-ios#conforming-to-objective-c-swift-protocols-in-nativescript)
 
 ## Objective-C Selectors
@@ -272,12 +274,12 @@ UIView *view = [[UIView alloc] initWithFrame:rect];
 const rect = {
   origin: {
     x: 0,
-    y: 0
+    y: 0,
   },
   size: {
     width: 100,
-    height: 100
-  }
+    height: 100,
+  },
 }
 const view = UIView.alloc().initWithFrame(rect)
 ```
@@ -350,4 +352,4 @@ const exists = fileManager.fileExistsAtPathIsDirectory('/var/log', isDirectory)
 if (isDirectory.value) {
   console.log('The path is actually a directory')
 }
-```
+```

content/guide/ios-marshalling.md

@@ -4,43 +4,40 @@ title: iOS Runtime Types
 
 NativeScript provides the `interop` module for working with native C types, pointers, pointer arithmetic and memory.
 
-
 <!-- TODO: Add examples -->
 
 ## Using interop
 
 ### Creating a pointer
 
-The `Pointer` type allows you to represent a void*.
+The `Pointer` type allows you to represent a void\*.
 
 #### Using the constructor
 
 To create a new pointer with the given offset, use the constructor:
 
 ```ts
-   const interop1 = new interop.Pointer(34)
+const interop1 = new interop.Pointer(34)
 ```
 
 #### Creating a pointer by adding an offset from an existing pointer
 
- ```ts
+```ts
 const interop2 = interop1.add(4)
- ```
+```
 
 #### Creating a pointer by removing an offset to an existing pointer
 
- ```ts
+```ts
 const interop3 = interop1.subtract(3)
- ```
+```
 
 ## interop API
 
 ### Pointer.toNumber()
 
 ```ts
-
 pointerInstance.toNumber()
-
 ```
 
 Converts the value of a `Pointer` instance to a number.
@@ -78,6 +75,7 @@ Releases the memory of the specified unadopted pointer.
 interop.sizeof(type: any): number
 
 ```
+
 Returns the size of the provided type. The `type` can be: a class constructor (of Objective-C interface), an instance (wrapper of Objective-C interface), struct constructor, struct instance, reference, protocol, function (for c function), fundamental types
 
 ---
@@ -118,7 +116,6 @@ Wraps an NSData instance in an ArrayBuffer.
 
 ---
 
-
 ### new Reference(value)
 
 Creates a new reference around a JavaScript `value`. The native representation of the type will be determined during the first time the Reference is used in an operation involving marshalling.
@@ -143,7 +140,6 @@ Creates a function reference that can be marshalled as a native function pointer
 
 ### interop types
 
-
 - "void": Type\<void\>
 - bool: Type\<boolean\>
 - int8: Type\<number\>
@@ -165,7 +161,7 @@ Creates a function reference that can be marshalled as a native function pointer
 - "class": Type\<any\>
 - selector: Type\<string\>
 
-----
+---
 
 ### new StructType()
 
@@ -180,11 +176,12 @@ Create a new instance of the struct and initialize it from the fields of the pro
 ---
 
 ### equals
+
 ```ts
 someStructTypeIntastance.equals(left: T, right: T): boolean
 
 ```
 
 Checks two structs for equality.
 
----
+---

content/guide/ios-runtime-types.md

@@ -75,7 +75,9 @@ Missing metadata entities could result in bugs at runtime. For example, if a nat
 - On Android they are located in `platforms/android/build-tools/buildMetadata.log`
 
 For each global symbol that is discovered by the generator, there should be a line providing information whether it was included in the metadata or not, and which rules or what exception caused this. Examples:
+
 <!-- TODO: An example of the following -->
+
 - `verbose: Blacklisted kCFBuddhistCalendar from CoreFoundation.CFLocale (disabled by 'CoreFoundation*:*')` - when there are no whitelist rules a blacklisted symbol will show only the rule which disabled it
 - `verbose: Blacklisted NSString from Foundation.NSString` - when there is at least one whitelist rule, some blacklisted symbols will not specify a rule. This means that the symbol didn't match any of the whitelist rules.
 - `verbose: Blacklisted PHImageContentModeDefault from Photos.PhotosTypes (enabled by 'Photos.PhotosTypes:*', disabled by 'Photos.PhotosTypes:PHImageContentMode*')`, `verbose: Blacklisted String from java.lang (enabled by java.lang:*, disabled by java.lang:String)` - a blacklisted entry which matches both a whitelist rule and a blacklist rule will specify both.
@@ -131,4 +133,3 @@ if (android.os.Build.VERSION.SDK_INT >= 21) {
 ## iOS Metadata
 
 This is our own custom data format for listing the iOS APIs we are aware of and can handle. It stores the minimal required information and provides a small size and highly efficient read access. iOS supports type introspection to some extent but along with the C APIs embedded all the way in the native APIs we had to store a lot of extra information. The Metadata is pre-generated at compile time from the SDK header files and embedded in the app package (ipa).
-