yungwarlock

#!/usr/bin/env bash

# Initialize all the option variables.
# This ensures we are not contaminated by variables from the environment.
file=
verbose=0

show_help() {
  echo "Hello"
}

yungwarlock

You can learn more about it in this issue

bazelbuild/rules_python#330

The fix that worked for me was using the comment

bazelbuild/rules_python#330 (comment)

Prevent creation of empty init.py

yungwarlock

def insertionsort(A):
    #we start loop at second element (index 1) since the first item is already sorted
    for j in range(1,len(A)):
        key = A[j] #The next item we are going to insert into the sorted section of the array

        i = j-1 #the last item we are going to compare to
        #now we keep moving the key back as long as it is smaller than the last item in the array
        while (i >= 0) and key < A[i]: #if i == -1 means that this key belongs at the start
            A[i+1]=A[i] #move the last object compared one step ahead to make room for key
            i=i-1 #observe the next item for next time.

yungwarlock

import React from 'react';
import useFeatureFlag from './useFeatureFlag';
import RecommendationsComponent from './Recommendations.js';

const { 
  DecoratedComponent: Recommendations, 
  featureEnabled: recommendationsFeatureEnabled,
  FeatureFlag
} = useFeatureFlag({
  Component: RecommendationsComponent,

yungwarlock

Directory structure for JavaScript/Node Projects

While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.

Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.

Directories

• lib/ is intended for code that can run as-is
• src/ is intended for code that needs to be manipulated before it can be used

yungwarlock

Git Best Practices

This is a fairly common question, and there isn't a One True Answer, but still, this represents a consensus from #git

Read about git

Knowing where to look is half the battle. I strongly urge everyone to read (and support) the Pro Git book. The other resources are highly