Matt Finucane matfin

Engineering questions

When's the right time to move functionality to a custom hook In React?

The main reasons to keep certain functinality outside of a hook are as follows:

It encourages reuse of code and keeps the complexity of a component down, by moving business logic outside of the component.
Moving functionality outside of a hook makes the component easier to test
Hooks are easy to initialise when needed, and their functionality can be discarded when no longer needed.

Here is an example of a custom hook I have written

This describes how to deal with custom content types and hooks in a Meteor JS based webapp which pulls its content from Contentful.

My goal was to reload content into a Meteor server side collection and have it update any time a user on Contentful.com updated content there. Contentful provide a very helpful hook mechanism, whereby a POST request is made to an endpoint of your choosing when content has been updated.

I was using the server side component of IronRouter to listen for incoming POST requests from Contentful and when they arrived, the request body was empty. This is because Contentful have a custom content type 'application/vnd.contentful.management.v1+json' and IronRouter does not know how to deal with that out of the box.

I wrote the above, using the nodejs connect and the body parser module. Want to know how to include these in your Meteor app? Look at this handy package - https://github.com/meteorhacks/npm which allows you to include NPM modules in meteor.

Look at line 15 in the above cod

	// From: https://twitter.com/rauschma/status/1487086371760136195?s=20&t=z_0I28Cjhgn1igKt90qmrw
	import assert from 'assert/strict';

	interface Character {
	name: string;
	}

	interface PrioritisedItem {
	name: string;
	priority: number;

	const courses = [
	{
	"courseData" : [
	{
	"course" : {
	"day" : "Tuesday",
	"duration" : "10 weeks",
	"language" : "German",
	"location" : "Online",
	"startdate" : "12th January",

	const hammerTime = async (url, numCalls) => {
	const start = performance.now();
	const results = [];

	for(let i = 0; i < numCalls; i++) {
	const res = await fetch(url);
	const data = await res.text();

	results.push(data);
	}

	((): void => {
	interface IItem {
	original: string,
	sorted: string
	}

	const test_inputs: string[] =[
	'poh', 'own', 'won', 'cat', 'eti', 'pat',
	'hpo', 'apt', 'now', 'tap', 'hop', 'tie'
	];

	<!DOCTYPE html>
	<html>
	<head>
	</head>
	<body>

	<!-- Option One -->
	<!--pluralsight-comment></pluralsight-comment-->

	<script type="text/javascript">

	/**
	* A practical example of using Fibers in Meteor JS
	*/

	var MeteorFiber = {

	takeLong: function() {
	var future = new this.Future();
	Meteor.setTimeout(function() {
	/**

	var numbers = [1, 1, 2, 3, 2, 3, 7, 8, 8];

	var getOddOccurrence = function(numbers) {
	var collected = [],
	keys,
	oddnum;

	numbers.forEach(function(number) {
	if(typeof collected[number] === 'undefined') {
	collected[number] = [];

	'use strict';

	/**
	* Given an object map like this one
	*/

	var map = {
	objectOne: {
	attributeOne: 1,
	attributeTwo: 2