mjurincic

const axios = require('axios');
const { GarminConnect } = require('garmin-connect');
const GCClient = new GarminConnect();


const getExistingActivities = async () => {
  const existingActivityIds = []
  const activities = await axios.get(`${process.env.HOST}/activities`)
  activities.data.map((activity) => {
    existingActivityIds.push(activity.activityId)

mjurincic

Change scrollback limit for tmux buffer on iterm

Original stackoverflow post here

Solution

• iTerm2 build 1.0.0.20130302 has an preference which enables it to capture scrollback even when a so-called hard status line is present:
  • https://i.stack.imgur.com/QS1vB.png
  • Preferences -> Terminal -> check "Save lines to scrollback when an app status bar is present"
• maybe also check "Save lines to scrollback in alternate screen mode"

mjurincic

import { FormGroup, ValidationErrors } from '@angular/forms';

export function getFormValidationErrors(form: FormGroup) {

  const result = [];
  Object.keys(form.controls).forEach(key => {

    const controlErrors: ValidationErrors = form.get(key).errors;
    if (controlErrors) {
      Object.keys(controlErrors).forEach(keyError => {

mjurincic

Sending email with serverless functions

You can deploy this function on any of the serverless platforms - AWS Lambda, Google Cloud Functions, Azure Functions, Netlify, Cloudflare Workers, etc.

1. Create a new function and paste in the following code.
2. You will need to add nodemailer to your package.json (npm i nodemailer), and follow your platform's instructions on bundling dependencies.
3. Obtain Gmail API credentials for your account. You will need clientID, clientSecret, and refreshToken. Follow this YouTube tutorial
4. Expose these credentials as the follwing environment variables:

GMAIL_EMAIL_ADDRESS

mjurincic

Handle CORS Client-side

Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources (e.g. fonts) on a web page to be requested from another domain outside the domain from which the first resource was served. This is set on the server-side and there is nothing you can do from the client-side to change that setting, that is up to the server/API. There are some ways to get around it tho.

Sources : MDN - HTTP Access Control | Wiki - CORS

CORS is set server-side by supplying each request with additional headers which allow requests to be requested outside of the own domain, for example to your localhost. This is primarily set by the header:

Access-Control-Allow-Origin

mjurincic

import { Country, Photon } from '@prisma/photon';
import { findManyCursor } from './findManyCursor';

const photon = new Photon();

let data: Country[];

const createCountry = async (id: string) => photon.countries.create({
  data: {
    id,

mjurincic

import { Country, Photon } from '@prisma/photon';
import { findManyCursor } from './findManyCursor';

const photon = new Photon();

let data: Country[];

const createCountry = async (id: string) => photon.countries.create({
  data: {
    id,

mjurincic

<?
/////////////////////
// slack2html
// by @levelsio
/////////////////////
//
/////////////////////
// WHAT DOES THIS DO?
/////////////////////
//

mjurincic

RewriteEngine on

RewriteCond %{HTTP:X-Forwarded-Proto} !https 
RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

mjurincic

// place in pages/sitemap.xml.tsx

const fs = require('fs')
import { endpoint } from '../config'

const Sitemap = () => null
Sitemap.getInitialProps = async ({ res }) => {
  if (!res) return {}
  const folder = 'pages'
  res.setHeader('content-type', 'application/xml')