Oxyrus

How to have dependency injection and parameters at the same time?

Recently I needed to have a custom authorization attribute to use in my .NET API, where I needed to have some dependency injected services but also pass in an argument to the attribute. I hope this can help you:

enum Feature
{
    Articles,
    Comments
}

Oxyrus

go: extracting google.golang.org/grpc v1.13.0
-> unzip C:\Users\USUARIO\go\src\mod\cache\download\google.golang.org\grpc\@v\v1.13.0.zip: invalid file name google.golang.org/[email protected]/.github/ISSUE_TEMPLATE
go: extracting github.com/kelseyhightower/envconfig v1.3.0
-> unzip C:\Users\USUARIO\go\src\mod\cache\download\github.com\kelseyhightower\envconfig\@v\v1.3.0.zip: invalid file name github.com/kelseyhightower/[email protected]/.travis.yml
go: extracting github.com/golang/protobuf v1.1.0
-> unzip C:\Users\USUARIO\go\src\mod\cache\download\github.com\golang\protobuf\@v\v1.1.0.zip: invalid file name github.com/golang/[email protected]/.gitignore
go: downloading github.com/vektah/gqlgen v0.0.0-20180710015341-ac9e5a66f879
-> unzip C:\Users\USUARIO\go\src\mod\cache\download\github.com\vektah\gqlgen\@v\v0.0.0-20180710015341-ac9e5a66f879.zip: invalid file name github.com/vektah/[email protected]/.circleci/config.yml
go: extracting github.com/tinrab/retry v1.0.0
-> unzip C:\Users\USUARIO\go\sr

Oxyrus

We subscribe to the Git Featrue Branch workflow, briefly described in that link.

In practice, it works as follows:

FEATURE DEVELOPMENT

Steps to Follow:

1. Start with an updated local development branch -- by checking out the dev branch and pulling changes:
   git checkout development
git pull origin development

Oxyrus

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

Oxyrus

Using git-submodules to version-control Vim plugins

If you work across many computers (and even otherwise!), it's a good idea to keep a copy of your setup on the cloud, preferably in a git repository, and clone it on another machine when you need. Thus, you should keep the .vim directory along with your .vimrc version-controlled.

But when you have plugins installed inside .vim/bundle (if you use pathogen), or inside .vim/pack (if you use Vim 8's packages), keeping a copy where you want to be able to update the plugins (individual git repositories), as well as your vim-configuration as a whole, requires you to use git submodules.

Creating the repository

Initialize a git repository inside your .vim directory, add everything (including the vimrc), commit and push to a GitHub/BitBucket/GitLab repository:

cd ~/.vim

Oxyrus

" Vim color file
" Converted from Textmate theme Ariake using Coloration v0.4.0 (http://github.com/sickill/coloration)

set background=dark
highlight clear

if exists("syntax_on")
  syntax reset
endif

Oxyrus

type CacheInterface interface {
  Get(key string) ([]byte, error)
  Set(key string, value interface{}) error
}

// Cache implements CacheInterface.
type Cache struct {
  // wrap redis pool connection
  // or whatever you need
}

Oxyrus

type (
	// BuoyCondition contains information for an individual station.
	BuoyCondition struct {
		WindSpeed     float64 `bson:"wind_speed_milehour"`
		WindDirection int     `bson:"wind_direction_degnorth"`
		WindGust      float64 `bson:"gust_wind_speed_milehour"`
	}
 
	// BuoyLocation contains the buoy's location.
	BuoyLocation struct {

Oxyrus

// components/Login/Login.js

class Login extends Component {
  
  // ...
  
  handleSubmit(evt) {
    evt.preventDefault();
    this.props.mutate(this.state)
      .then(({ data }) => {

Oxyrus

import React, { Component, PropTypes } from 'react';
import { graphql } from 'react-apollo';
import gql from 'graphql-tag';

class App extends Component {  
  render() {
    if (!this.props.data.posts) {
      return null;
    }
    return (