Henry S hsavit1

## shadcn-ui react-select.jsx
/* ----------- simple-select.js ----------- */
import * as React from 'react';
import Select from 'react-select';
import type { Props } from 'react-select';
import { defaultClassNames, defaultStyles } from './helper';
import {
  ClearIndicator,
  DropdownIndicator,
  MultiValueRemove,
  Option

## SwiftUIViewModule.swift
import ExpoModulesCore
import SwiftUI

public class SwiftuiViewModule: Module {
  public func definition() -> ModuleDefinition {
    Name("SwiftuiForm")
      View(SwiftuiView.self) {
          Prop("name") { (view, name: String) in
              view.name = name
          }

## mirage-graphql-example.js
import { buildSchema, graphql } from "graphql";

// Construct a schema, using GraphQL schema language
let graphqlSchema = buildSchema(`
  type Query {
    recipes: [Recipe]
    recipes_by_pk(id: Int!): Recipe
  }
  type Recipe {
    id: ID!

## sql_parser.exs
defmodule SqlParser do
  def run() do
    input = "select col1 from (
      select col2, col3 from (
        select col4, col5, col6 from some_table
      )
    )
    "
    IO.puts("input: #{inspect(input)}\n")
    IO.inspect(parse(input))

## WhyReact.md

      
              1 file
            
          
              15 forks
            
          
              26 comments
            
          
              263 stars
            
          
                sebmarkbage
                / WhyReact.md
            
            
              Created
              September 4, 2019 20:33
            
              
                Why is React doing this?
              
          
    I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.
I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.
"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr

  
## everything-i-know-about-routing.md

      
              1 file
            
          
              34 forks
            
          
              9 comments
            
          
              328 stars
            
          
                ryanflorence
                / everything-i-know-about-routing.md
            
            
              Last active
              November 2, 2024 12:17
            
          
    Everything I Know About UI Routing

Definitions


Location - The location of the application. Usually just a URL, but the location can contain multiple pieces of information that can be used by an app

pathname - The "file/directory" portion of the URL, like invoices/123
search - The stuff after ? in a URL like /assignments?showGrades=1.
query - A parsed version of search, usually an object but not a standard browser feature.
hash - The # portion of the URL. This is not available to servers in request.url so its client only. By default it means which part of the page the user should be scrolled to, but developers use it for various things.
state - Object associated with a location. Think of it like a hidden URL query. It's state you want to keep with a specific location, but you don't want it to be visible in the URL.


## rebuilding_espec_macro_resource_links.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              1 star
            
          
                treble37
                / rebuilding_espec_macro_resource_links.md
            
            
              Last active
              March 15, 2020 22:22
            
              
                Rebuilding a BDD Framework (ESpec) Metaprogramming Resource Links
              
          
    Blogs

Understanding Elixir Macros, Part 1 by Saša Jurić
Understanding Elixir Macros, Part 2 (Part 3 Part 4 Part 5 Part 6)

Books

Metaprogramming Elixir by Chris McCord

Official Documentation

  
## phx-1.4-upgrade.md

      
              1 file
            
          
              14 forks
            
          
              33 comments
            
          
              121 stars
            
          
                chrismccord
                / phx-1.4-upgrade.md
            
            
              Last active
              October 14, 2024 09:32
            
              
                Phoenix 1.3.x to 1.4.0 Upgrade Guides
              
          
    Phoenix 1.4 ships with exciting new features, most notably with HTTP2 support, improved development experience with faster compile times, new error pages, and local SSL certificate generation. Additionally, our channel layer internals receiveced an overhaul, provided better structure and extensibility. We also shipped a new and improved Presence javascript API, as well as Elixir formatter integration for our routing and test DSLs.
This release requires few user-facing changes and should be a fast upgrade for those on Phoenix 1.3.x.
Install the new phx.new project generator

The mix phx.new archive can now be installed via hex, for a simpler, versioned installation experience.
To grab the new archive, simply run:

  
## spa.html
<!DOCTYPE html>
<html lang="en">

<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta http-equiv="X-UA-Compatible" content="ie=edge">
  <title>SPA - demo</title>
  <style>
    .page {

## index.html
<!DOCTYPE html>
<html>
  <head>
    <meta charset="UTF-8" />
    <title>Add React in One Minute</title>
  </head>
  <body>

    <h2>Add React in One Minute</h2>
    <p>This page demonstrates using React with no build tooling.</p>
	/* ----------- simple-select.js ----------- */
	import * as React from 'react';
	import Select from 'react-select';
	import type { Props } from 'react-select';
	import { defaultClassNames, defaultStyles } from './helper';
	import {
	ClearIndicator,
	DropdownIndicator,
	MultiValueRemove,
	Option
	import ExpoModulesCore
	import SwiftUI

	public class SwiftuiViewModule: Module {
	public func definition() -> ModuleDefinition {
	Name("SwiftuiForm")
	View(SwiftuiView.self) {
	Prop("name") { (view, name: String) in
	view.name = name
	}
	import { buildSchema, graphql } from "graphql";

	// Construct a schema, using GraphQL schema language
	let graphqlSchema = buildSchema(`
	type Query {
	recipes: [Recipe]
	recipes_by_pk(id: Int!): Recipe
	}
	type Recipe {
	id: ID!
	defmodule SqlParser do
	def run() do
	input = "select col1 from (
	select col2, col3 from (
	select col4, col5, col6 from some_table
	)
	)
	"
	IO.puts("input: #{inspect(input)}\n")
	IO.inspect(parse(input))
	<!DOCTYPE html>
	<html lang="en">

	<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<meta http-equiv="X-UA-Compatible" content="ie=edge">
	<title>SPA - demo</title>
	<style>
	.page {
	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="UTF-8" />
	<title>Add React in One Minute</title>
	</head>
	<body>

	<h2>Add React in One Minute</h2>
	<p>This page demonstrates using React with no build tooling.</p>