Truong Hoang Dung revskill10

## jsx-dom.html
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Document</title>
  </head>
  <body>
    <div id="app"></div>
    <script type="module">

## auto-dr.md

      
              1 file
            
          
              5 forks
            
          
              0 comments
            
          
              79 stars
            
          
                yzdbg
                / auto-dr.md
            
            
              Last active
              November 3, 2023 17:11
            
          
    Automating Daily Reports, because fuck it, really...

Each day at our company, developers are required to document their activities, painstakingly jotting down their daily work and future plans. A monotonous chore that I just really dislike.
So now, there's a scribe for that :

Code


## for-loop.md

      
              1 file
            
          
              0 forks
            
          
              3 comments
            
          
              10 stars
            
          
                nicolo-ribaudo
                / for-loop.md
            
            
              Last active
              June 4, 2023 20:49
            
          
    This for loop:
for (let i = 0, getI = () => i; i < 3; i++)
  console.log(getI());
unrolls to:


## stage.tsx
// TODO: make `pages` optional and measure the div when unspecified, this will
// allow more normal document flow and make it easier to do both mobile and
// desktop.
import {
  createContext,
  useCallback,
  useContext,
  useEffect,
  useMemo,
  useRef,

## combine-provider.tsx
import { ComponentProps, FC, Fragment } from "react";

export interface ProvidersProps {
  children: React.ReactNode;
}

export type ProviderWithProps = [FC<ProvidersProps>, Object];

/**
 * Function that combines all the context providers into a single one.

## index.md

      
              1 file
            
          
              5 forks
            
          
              6 comments
            
          
              56 stars
            
          
                GavinRay97
                / index.md
            
            
              Last active
              April 12, 2024 18:31
            
              
                Hasura organization permissions
              
          
    Introduction

This document outlines how to model a common organization-based permission system in Hasura. Let's assume that you have some table structure like the following:


Table Name
Columns
Foreign Keys


User
id, name, email


Organization User
id, user_id, organization_id
user_id -> user.id, organization_id -> organization.id


Organization
id, name


## createResource.js
import React from "react";
import { Link } from "react-router-dom";

export function createResource(getPromise) {
  let cache = {};
  let inflight = {};
  let errors = {};

  function load(key) {
    inflight[key] = getPromise(key)

## PG_EXTN_C_WITH_RUST.md

      
              1 file
            
          
              2 forks
            
          
              0 comments
            
          
              8 stars
            
          
                ranjanprj
                / PG_EXTN_C_WITH_RUST.md
            
            
              Last active
              November 9, 2019 18:10
            
              
                PostgreSQL Extension in C with Rustlang
              
          
    Just a small gist to show how you can easily create a Rust shared lib, wrap it with C and call it from PostgreSQL SQL Command.


Prereq : Tested on Ubuntu 18, GCC, postgresql-server-11, postgresql-dev-11, rustlang
Create new project Cargo embed and cd embed
Rename the file src/main.rs to lib.rs
Add following code

#[no_mangle]
pub extern fn double_input(input: i32) -> i32 {
    input * 2


## 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

  
## login.jsx
import React from "react"
import PropTypes from "prop-types"

export default class LogIn extends React.Component {
  constructor(props) {
    super(props);
    this.state = {
      email: '',
      email_ready: undefined,
      password: '',
	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8" />
	<meta name="viewport" content="width=device-width, initial-scale=1.0" />
	<title>Document</title>
	</head>
	<body>
	<div id="app"></div>
	<script type="module">
	// TODO: make `pages` optional and measure the div when unspecified, this will
	// allow more normal document flow and make it easier to do both mobile and
	// desktop.
	import {
	createContext,
	useCallback,
	useContext,
	useEffect,
	useMemo,
	useRef,
	import { ComponentProps, FC, Fragment } from "react";

	export interface ProvidersProps {
	children: React.ReactNode;
	}

	export type ProviderWithProps = [FC<ProvidersProps>, Object];

	/**
	* Function that combines all the context providers into a single one.
Table Name	Columns	Foreign Keys
User	id, name, email
Organization User	id, user_id, organization_id	user_id -> user.id, organization_id -> organization.id
Organization	id, name
	import React from "react";
	import { Link } from "react-router-dom";

	export function createResource(getPromise) {
	let cache = {};
	let inflight = {};
	let errors = {};

	function load(key) {
	inflight[key] = getPromise(key)
	import React from "react"
	import PropTypes from "prop-types"

	export default class LogIn extends React.Component {
	constructor(props) {
	super(props);
	this.state = {
	email: '',
	email_ready: undefined,
	password: '',