isocroft

expect.extend({
  toBeArrayContainingObject(received, argument) {

    const pass = this.equals(received, 
      expect.arrayContaining([
        expect.objectContaining(argument)
      ])
    )

    if (pass) {

isocroft

import React, { useState } from "react";
import { render, act, waitFor } from "@testing-library/react";
import userEvent from "@testing-library/user-event";
import { roles, Components } from "constants/ui-copy";

function RecipeForm ({ onSubmit }) {
  function formToObject(form) {
    const formData = new FormData(form);
    return Object.fromEntries(formData.entries());
  }

isocroft

import React, { useRef, useEffect } from "react";
import Button from "./Button";
import type { ButtonProps } from "./Button";

import { useAuthTokenFromContext } from "../AuthProvider"; 

export const HttpButton = ({
  children,
  action,
  enctype = "application/x-www-form-urlencoded",

isocroft

Reader-Tagged Comments Specification

A handy standard specification proposal for writing very useful comments directed at anyone reading software source code with aided understanding as the primary objective.

[1]. Front Matter

• Title: Reader-Tagged Comments Specification
• Author(s): Ifeora Okechukwu Patrick
• Team: self
• Reviewer(s): Eze Sunday Eze, Pascal Oraizu

isocroft

Introduction To Structured Concurrency In Javascript, Python And Go

[PRIMER]: The 2 Models Of Concurrency

Threads are usually misunderstood. There are not all bad. They have simply been dealt a bad hand with pre-emptive scheduling and all its' attendant consequences e.g. locks and busy waits. Once threads are implemented using immutable variables, atomic message queues and cooperative scheduling, they operate much better. Sadly, there's little we can do about the overhead of state management for threads.

1. Thread-based model of concurrency (e.g. well, Threads)
2. Event-based model of concurrency (e.g. Actors + mailbox, E

isocroft

<?php
  namespace Parlie\Traits\Routing\Middleware\Guard;

  use Closure;
  use Illuminate\Http\Request;
  use Symfony\Component\HttpFoundation\Response;


  trait ApplyTenantRouteGuard {
    

isocroft

Practical Guidelines For Writing Great Tests In Imperative-styled Programming Languages (e.g Go, Python, Rust, JavaScript)

Common Testing Issues

All common issues with tests from flaky tests to brittle and tests can all be traced back to either coupling or dangling side-effects.

There are several types of coupling that can affect tests as follows:

• Temporal coupling (timing cross-dependencies e.g. race conditions)
• Stamp/Common coupling (state share/ownership cross-dependencies e.g. 2 or more test cases sharing the same stub or mock references)

isocroft

const isPromise = () => {

};

const isPrimitive = (target) => {
  return ['number', 'boolean', 'string'].includes(typeof target);
};

const isError = (target) => {
  if (!(target instanceof Object)) {

isocroft

//import { ZipkinExporter } from "@opentelemetry/exporter-zipkin";
import api, { Span, SpanStatusCode, SpanOptions, SpanKind } from "@opentelemetry/api";

import { OTLPTraceExporter } from "@opentelemetry/exporter-otlp-http";
import { WebTracerProvider } from "@opentelemetry/sdk-trace-web";
import { SimpleSpanProcessor, ConsoleSpanExporter, BatchSpanProcessor } from "@opentelemetry/sdk-trace-base";
import { ZoneContextManager } from "@opentelemetry/context-zone";
import { Resource } from "@opentelemetry/resources";
import { SemanticResourceAttributes } from "@opentelemetry/semantic-conventions";
import { registerInstrumentations } from "@opentelemetry/instrumentation";

isocroft

<?php

/**
 * To truly decouple one dependent code from another dependency, there must be full collaboration
 * or full disaffiliation. There are no in-betweens
 *
 * The Open-Close principle gets in the way of that: 
 *
 * See: https://isocroft.medium.com/the-open-close-principle-is-backwards-and-broken-930646d92f8b
 */