yordis

defmodule MyAppWeb.Schema.Middleware.AuthorizedIntrospection do
  @moduledoc """
  Disable or restrict schema introspection to authorized requests
  """
  @behaviour Absinthe.Plugin

  @impl Absinthe.Plugin
  def before_resolution(%{context: %{admin: true}} = exec), do: exec

  def before_resolution(exec) do

yordis

import * as assert from "assert";

/** Decider Pattern **/

type Transaction = {
    amount: number
    date: Date
}

type Deposited = Transaction & {

yordis

Mix.install([:httpoison, :poison])

defmodule Spotify do
  [playlist_id] = System.argv()

  @token_url "https://accounts.spotify.com/api/token"
  @playlist_url "https://api.spotify.com/v1/playlists/#{playlist_id}"

  def get_token() do
    client_id = System.get_env("SPOTIFY_CLIENT_ID")

yordis

#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# Log Reader - polls log file and sends new lines to channel
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
defmodule LogReader do
  use GenServer

  @log_file "priv/some_log.log"
  @poll_interval 5 * 1000 # 5 seconds

  def run_test() do

yordis

Erlang GitHub Actions With setup-beam and Caching

To build and test Erlang projects on GitHub actions with Rebar 3 it is fastest to use the setup-beam action and use caching.

To get started, create a workflow file in .github/workflows in your repository. For this example we use a file called .github/workflows/continuous_integration.yml.

yordis

defmodule Mix.Tasks.InspectAggregate do
  use Mix.Task

  alias MyApp.EventStore

  def run(args) do
    Application.ensure_all_started(:eventstore)
    _ = EventStore.start_link()

    {opts, _} =

yordis

Commanded middleware for command enrichment

Usage

Add the EnrichCommand middleware to your command router:

defmodule MyApp.Router do
  use Commanded.Commands.Router
 

yordis

This is way more complicated than it should be. The following conditions need to be met :

1. need to be able to track and merge in upstream changes
2. don't want remote commit messages in master
3. only interested in sub-directory of another repo
4. needs to go in a subdirectory in my repo.

In this particular case, I'm interested in bringing in the 'default' template of jsdoc as a sub-directory in my project so I could potentially make changes to the markup it genereates while also being able to update from upstream if there are changes. Ideally their template should be a separate repo added to jsdoc via a submodule -- this way I could fork it and things would be much easier.... but, it is what it is.

After much struggling with git, subtree and git-subtree, I ended up finding this http://archive.h2ik.co/2011/03/having-fun-with-git-subtree/ -- it basically sets up separate branches from tracking remote, the particular sub-directory, and uses git subtree contrib module to pull it all togther. Following are

yordis

defmodule EventStore.CategoryStreamLinker do
  @moduledoc """
    Links streams from aggregate instances to their respective category streams.

    example: events from stream_uuid of `contractors_contract-07c52787-da0c-444f-9783-5d380f7093f9` will be
    linked to stream_uuid of `contractors_contract`.
  """

  use Commanded.Event.Handler,
    application: My.App,

yordis

// helps us in parsing the frontmatter from text content
const matter = require('gray-matter')
// helps us safely stringigy the frontmatter as a json object
const stringifyObject = require('stringify-object')
// helps us in getting the reading time for a given text
const readingTime = require('reading-time')

// please make sure you have installed these dependencies
// before proceeding further, or remove the require statements
// that you don't use