Jamie Birch shirakaba

By executing the following code snippet in NS:IDE, we can see which native APIs have been exposed to JS, at least in the global context:

Object.keys(global).sort();

Thus, we can see that the following keys exist on the global object, most of which are iOS APIs. There is also precious little overlap with Node.js's global interface.

Dependency Injection

Dependency Injection (DI) is used to invert control in portions of a program. Here I focus on the concrete use-case of provisioning a class with a logger implementation that keeps a class-instance loggingInfo object so that any call to the logger will always include the info from loggingInfo (e.g. an id for a request that the class instance was constructed solely to handle) in its log messages.

In my implementations, I refer to global.wi, global.wd and other similarly cryptically-named methods; these stand for "Winston info-level log" and "Winston debug-level log", etc. (where Winston is the logging library I normally use). At the start of the program, it is assumed that one would register an implementation to these variables – typically a call to a Winston logger, but could equally be substituted for console.log.

Patterns

I wanted to investigate two key ways of augmenting existing classes, ultimately to achieve depen

Bridging header

Purpose

While you can't import Objective-C headers directly in Swift files, you can import them all into a bridging header file, which will subsequently be exposed to your Swift environment throughout the project.

Thus, you should write into the bridging header the union of all headers you'll be referring to (e.g. due to invoking APIs or asserting types) in your Swift code.

For a React Native project, the fundamental headers you'll need come from the React static library. If you call upon any native modules, you'll need to import their headers, too.

Passing resolve/reject handlers on to event listeners

import * as cp from "child_process";

function promisifiedSpawn(cmd, spawnArgsArray){
  return new Promise((resolve, reject) => {
    const cp = cp.spawn(cmd, spawnArgsArray);
    cp.on("exit", onExit.bind(this, resolve, reject));
 }

Get the details to connect to your Nexus-managed npm repository

Note: Nexus group repositories (good example in this StackOverflow question) are out of this tutorial's scope. In any case, deployment to group repositories is currently still an open issue for Nexus 3 (and not intended ever to be implemented in Nexus 2). Thus, it is assumed that we'll push & pull to/from the same repository, and ignore the idea of groups hereon in.

Ask your sysadmin for a username & password allowing you to log into your organistation's Nexus Repository Manager.
Test the login credentials on the Nexus Repository manager at: http://localhost:8081/nexus/#view-repositories (localhost in our case is replaced by a static IP, and can only be connected to over VPN). If your organisation requires a VPN to connect to it, connect to that VPN before proceeding with this tutori

	import * as console from "react-nativescript/dist/shared/Logger";
	import * as React from "react";
	import { PropsWithoutForwardedRef } from "react-nativescript/dist/shared/NativeScriptComponentTypings";
	import { TextViewWithHint as NativeScriptTextViewWithHint } from "@nativescript/core";
	import { _TextView, TextViewComponentProps } from "react-nativescript/dist/components/TextView";
	import { RNSFriendly } from "react-nativescript/dist/components/TextBase";
	import { updateListener } from "react-nativescript/dist/client/EventHandling";
	import { Container, HostContext, Instance } from "react-nativescript/dist/shared/HostConfigTypes";
	import { register } from "react-nativescript/dist/client/ElementRegistry";
	import { ContentViewProps, TextViewWithHintProps } from "react-nativescript/dist/shared/NativeScriptComponentTypings";

	import * as console from "react-nativescript/dist/shared/Logger";
	import * as React from "react";
	import { PropsWithoutForwardedRef } from "react-nativescript/dist/shared/NativeScriptComponentTypings";
	import { PreviousNextView as NativeScriptPreviousNextView, EventData } from "@nstudio/nativescript-camera-plus";
	import { _ContentView, ContentViewComponentProps } from "react-nativescript/dist/components/ContentView";
	import { updateListener } from "react-nativescript/dist/client/EventHandling";
	import { Container, HostContext, Instance } from "react-nativescript/dist/shared/HostConfigTypes";
	import { register } from "react-nativescript/dist/client/ElementRegistry";

	const elementKey: string = "previousNextView";

	import * as console from "react-nativescript/dist/shared/Logger";
	import * as React from "react";
	import { PropsWithoutForwardedRef } from "react-nativescript/dist/shared/NativeScriptComponentTypings";
	import { CameraPlus as NativeScriptCameraPlus, EventData } from "@nstudio/nativescript-camera-plus";
	import { _ContentView, ContentViewComponentProps } from "react-nativescript/dist/components/ContentView";
	import { updateListener } from "react-nativescript/dist/client/EventHandling";
	import { Container, HostContext, Instance } from "react-nativescript/dist/shared/HostConfigTypes";
	import { register } from "react-nativescript/dist/client/ElementRegistry";

	const elementKey: string = "cameraPlus";

	#if canImport(UIKit)

	import UIKit

	UIApplicationMain(
	CommandLine.argc,
	CommandLine.unsafeArgv,
	NSStringFromClass(UIApplication.self),
	NSStringFromClass(AppDelegate.self)
	)