@finsemble/finsemble-core 6.1.4 → 6.1.5

package/dist/services/Interop/InteropServiceUI.tsx

@@ -1,39 +1,39 @@
-import React from "react";
-import ReactDOM from "react-dom";
-import { Provider, useDispatch, useSelector } from "react-redux";
-import InteropService from "./InteropService";
-import store from "./store";
-import { DevToolsContainer } from "./DevTools";
-import root from "./modules/root";
-import { InteropStore } from "./types";
-
-const HeartbeatButton = () => {
-	const dispatch = useDispatch();
-	const state: InteropStore = useSelector((currentState: any) => currentState);
-
-	const heartbeatAction = state.root.heartbeats ? "Stop Heartbeats" : "Start Heartbeats";
-
-	const toggleHeartbeats = () => {
-		dispatch(root.actions.toggleHeartbeats());
-	};
-
-	return <button onClick={toggleHeartbeats}>{heartbeatAction}</button>;
-};
-
-const InteropServiceUI = () => {
-	const blah = 0;
-
-	return (
-		<Provider store={store}>
-			<HeartbeatButton />
-			<div className="devTools">
-				<DevToolsContainer />
-			</div>
-		</Provider>
-	);
-};
-
-ReactDOM.render(<InteropServiceUI />, document.getElementById("InteropServiceUI-tsx"));
-
-// This line is necessary for the service to start, otherwise webpack thinks it's not being used and doesn't run the file InteropService.ts
-const interopService = InteropService;
+import React from "react";
+import ReactDOM from "react-dom";
+import { Provider, useDispatch, useSelector } from "react-redux";
+import InteropService from "./InteropService";
+import store from "./store";
+import { DevToolsContainer } from "./DevTools";
+import root from "./modules/root";
+import { InteropStore } from "./types";
+
+const HeartbeatButton = () => {
+	const dispatch = useDispatch();
+	const state: InteropStore = useSelector((currentState: any) => currentState);
+
+	const heartbeatAction = state.root.heartbeats ? "Stop Heartbeats" : "Start Heartbeats";
+
+	const toggleHeartbeats = () => {
+		dispatch(root.actions.toggleHeartbeats());
+	};
+
+	return <button onClick={toggleHeartbeats}>{heartbeatAction}</button>;
+};
+
+const InteropServiceUI = () => {
+	const blah = 0;
+
+	return (
+		<Provider store={store}>
+			<HeartbeatButton />
+			<div className="devTools">
+				<DevToolsContainer />
+			</div>
+		</Provider>
+	);
+};
+
+ReactDOM.render(<InteropServiceUI />, document.getElementById("InteropServiceUI-tsx"));
+
+// This line is necessary for the service to start, otherwise webpack thinks it's not being used and doesn't run the file InteropService.ts
+const interopService = InteropService;

package/dist/services/Interop/devtoolsEnhancer.tsx

@@ -1,63 +1,63 @@
-import { logMonitor } from "./DevTools";
-import { Children } from "react";
-import {
-	liftReducerWith as wrapReducerWithDevToolsProfiler,
-	unliftStore as unwrapDevToolsStore,
-	unliftState as unwrapDevToolsState,
-} from "redux-devtools-instrument";
-import { Reducer } from "@reduxjs/toolkit";
-import { StoreEnhancer } from "@reduxjs/toolkit";
-
-const monitorReducer = (state, action) => Children.only(logMonitor).type.update(logMonitor.props, state, action);
-
-/**
- * For performance reasons, we want to dynamically bypass DevTools functionality when it's not in use.
- *
- * We know DevTools is in use based on Interop service's window visible or the `visibility` value in the service's config
- *
- * In order to bypass DevTools, we have to create our own store enhancer that will initialize DevTools and then
- * dynamically choose which reducer to dispatch actions to based on what state we're in.
- *
- */
-export default (function (doCreateStore) {
-	return (currentReducer, preloadedState) => {
-		const wrappedReducer = wrapReducerWithDevToolsProfiler(
-			currentReducer,
-			preloadedState,
-			monitorReducer,
-			{}
-		) as Reducer;
-
-		let didInit = false;
-
-		const reducer = (wrappedState, wrappedAction) => {
-			if (!didInit) {
-				didInit = true;
-				return wrappedReducer(wrappedState, wrappedAction);
-			}
-
-			const unwrappedAction = wrappedAction.action;
-			const unwrappedState = unwrapDevToolsState(wrappedState);
-			const isWindowVisible = unwrappedState && unwrappedState.root.isVisible;
-			const isDevToolsAction = wrappedAction.type !== "PERFORM_ACTION" || !unwrappedAction;
-			const isBecomingVisible =
-				unwrappedAction && unwrappedAction.type === "root/windowVisible" && unwrappedAction.payload === true;
-
-			if (!isDevToolsAction && !isWindowVisible && !isBecomingVisible) {
-				// bypass DevTools reducer if devtools window isn't visible
-				wrappedState.computedStates[wrappedState.currentStateIndex].state = currentReducer(
-					unwrappedState,
-					unwrappedAction
-				);
-
-				return wrappedState;
-			}
-
-			return wrappedReducer(wrappedState, wrappedAction);
-		};
-
-		const wrappedStore = doCreateStore(reducer);
-
-		return unwrapDevToolsStore(wrappedStore, reducer as any, {});
-	};
-} as StoreEnhancer);
+import { logMonitor } from "./DevTools";
+import { Children } from "react";
+import {
+	liftReducerWith as wrapReducerWithDevToolsProfiler,
+	unliftStore as unwrapDevToolsStore,
+	unliftState as unwrapDevToolsState,
+} from "redux-devtools-instrument";
+import { Reducer } from "@reduxjs/toolkit";
+import { StoreEnhancer } from "@reduxjs/toolkit";
+
+const monitorReducer = (state, action) => Children.only(logMonitor).type.update(logMonitor.props, state, action);
+
+/**
+ * For performance reasons, we want to dynamically bypass DevTools functionality when it's not in use.
+ *
+ * We know DevTools is in use based on Interop service's window visible or the `visibility` value in the service's config
+ *
+ * In order to bypass DevTools, we have to create our own store enhancer that will initialize DevTools and then
+ * dynamically choose which reducer to dispatch actions to based on what state we're in.
+ *
+ */
+export default (function (doCreateStore) {
+	return (currentReducer, preloadedState) => {
+		const wrappedReducer = wrapReducerWithDevToolsProfiler(
+			currentReducer,
+			preloadedState,
+			monitorReducer,
+			{}
+		) as Reducer;
+
+		let didInit = false;
+
+		const reducer = (wrappedState, wrappedAction) => {
+			if (!didInit) {
+				didInit = true;
+				return wrappedReducer(wrappedState, wrappedAction);
+			}
+
+			const unwrappedAction = wrappedAction.action;
+			const unwrappedState = unwrapDevToolsState(wrappedState);
+			const isWindowVisible = unwrappedState && unwrappedState.root.isVisible;
+			const isDevToolsAction = wrappedAction.type !== "PERFORM_ACTION" || !unwrappedAction;
+			const isBecomingVisible =
+				unwrappedAction && unwrappedAction.type === "root/windowVisible" && unwrappedAction.payload === true;
+
+			if (!isDevToolsAction && !isWindowVisible && !isBecomingVisible) {
+				// bypass DevTools reducer if devtools window isn't visible
+				wrappedState.computedStates[wrappedState.currentStateIndex].state = currentReducer(
+					unwrappedState,
+					unwrappedAction
+				);
+
+				return wrappedState;
+			}
+
+			return wrappedReducer(wrappedState, wrappedAction);
+		};
+
+		const wrappedStore = doCreateStore(reducer);
+
+		return unwrapDevToolsStore(wrappedStore, reducer as any, {});
+	};
+} as StoreEnhancer);

package/dist/services/Interop/tsconfig.json

@@ -1,7 +1,7 @@
-{
-	"extends": "../../../tsconfig.json",
-	"compilerOptions": {
-		//"noImplicitAny": true,
-		"strict": true
-	}
-}
+{
+	"extends": "../../../tsconfig.json",
+	"compilerOptions": {
+		//"noImplicitAny": true,
+		"strict": true
+	}
+}

package/dist/services/ServiceTemplate.md

@@ -1,39 +1,39 @@
-\*\*\* See storageService for a template.
-
-Notes
-
-1. Endpoints inside of `createRouterEndpoints` should be grouped by endpoint type, and then alphabetized. All listeners
-   go together, then responders, then pub/sub responders. Remember that this isn't so that the code makes sense to the
-   guy who wrote it, it's to help someone unfamiliar with the code jump in and quickly understand what's going on.
-2. Router handlers should modify the incoming message (if necessary), and pass off any input into a member function.
-   When the member function is done, the router handler will interface directly with the router. If the member function
-   is big, hard to follow, and does async things, you should consider using async/await. In some cases this complicates
-   rather than simplifies the code, so use your discretion. Ask another dev if you're concerned.
-3. `initialize` should be the first member function.
-4. `createRouterEndpoints` should be the second member function.
-5. `bindCorrectContext` should be the third member function (if it's necessary).
-6. Member functions should be alphabetized, but getters and setters should be grouped. (e.g., Dingle, Eagle, Roger,
-   getStore, setStore, Truck).
-7. Put a global reference to the service on the window at the bottom of your file for quick debugging.
-8. Document each function. Include a description, and document the parameters that are passed in.
-9. _Logging_
-
-   - `error`: Should be obvious.
-
-   - `warn`: More contentious, but do your best. Generally, a warning for something that's wrong but not
-     system-critical. "Hey you shouldn't do this."
-
-   - `log`: Used for lifecycle notifications. E.g., Workspace load, window close, etc. If you aren't sure if it counts
-     as the application lifecycle, ask two other people to weigh in.
-
-   - `info`: Each entry point into the API should have `Logger.system.info(SERVICE_NAME.METHOD_NAME, description,
-     pertinentFunctionInput). Data should only be included if necessary.
-
-   - `debug`: Put debug messages around areas that you're likely to need to look at to solve problems later.
-
-   - `verbose`: Only the most egregious logs go here. E.g., assimilation/docking move events. Router client messages,
-     etc.
-
-Client-side
-
-1. Queries and transmitters should be wrapped in client functions. Only query/transmit from one place.
+\*\*\* See storageService for a template.
+
+Notes
+
+1. Endpoints inside of `createRouterEndpoints` should be grouped by endpoint type, and then alphabetized. All listeners
+   go together, then responders, then pub/sub responders. Remember that this isn't so that the code makes sense to the
+   guy who wrote it, it's to help someone unfamiliar with the code jump in and quickly understand what's going on.
+2. Router handlers should modify the incoming message (if necessary), and pass off any input into a member function.
+   When the member function is done, the router handler will interface directly with the router. If the member function
+   is big, hard to follow, and does async things, you should consider using async/await. In some cases this complicates
+   rather than simplifies the code, so use your discretion. Ask another dev if you're concerned.
+3. `initialize` should be the first member function.
+4. `createRouterEndpoints` should be the second member function.
+5. `bindCorrectContext` should be the third member function (if it's necessary).
+6. Member functions should be alphabetized, but getters and setters should be grouped. (e.g., Dingle, Eagle, Roger,
+   getStore, setStore, Truck).
+7. Put a global reference to the service on the window at the bottom of your file for quick debugging.
+8. Document each function. Include a description, and document the parameters that are passed in.
+9. _Logging_
+
+   - `error`: Should be obvious.
+
+   - `warn`: More contentious, but do your best. Generally, a warning for something that's wrong but not
+     system-critical. "Hey you shouldn't do this."
+
+   - `log`: Used for lifecycle notifications. E.g., Workspace load, window close, etc. If you aren't sure if it counts
+     as the application lifecycle, ask two other people to weigh in.
+
+   - `info`: Each entry point into the API should have `Logger.system.info(SERVICE_NAME.METHOD_NAME, description,
+     pertinentFunctionInput). Data should only be included if necessary.
+
+   - `debug`: Put debug messages around areas that you're likely to need to look at to solve problems later.
+
+   - `verbose`: Only the most egregious logs go here. E.g., assimilation/docking move events. Router client messages,
+     etc.
+
+Client-side
+
+1. Queries and transmitters should be wrapped in client functions. Only query/transmit from one place.

package/dist/services/assimilation/assimilation.html

@@ -1,18 +1,18 @@
-<!DOCTYPE html>
-<html>
-	<!--
-	 /*!
-    * Copyright 2017 - 2020 by ChartIQ, Inc.
-    * All rights reserved.
-    */
--->
-
-	<head>
-		<meta charset="utf-8" />
-		<title>Assimilation Service</title>
-	</head>
-
-	<body></body>
-
-	<script src="./assimilationService.js"></script>
-</html>
+<!DOCTYPE html>
+<html>
+	<!--
+	 /*!
+    * Copyright 2017 - 2020 by ChartIQ, Inc.
+    * All rights reserved.
+    */
+-->
+
+	<head>
+		<meta charset="utf-8" />
+		<title>Assimilation Service</title>
+	</head>
+
+	<body></body>
+
+	<script src="./assimilationService.js"></script>
+</html>