Skip to content

Instantly share code, notes, and snippets.

View Jarmahent's full-sized avatar
💭
Workaround master

Kevin Hernandez Jarmahent

💭
Workaround master
  • Rising Tide
  • Virginia
View GitHub Profile

Geting started with custom ESlint rules

Everyone can agree that Eslint is an extremely useful tool for programmers to keep their code looking nice and tidy for others, but sometimes Eslint doesnt provide a specific rule to some developers who are looking for a specific solution. Thankfully Eslint gives you the power to create your own custom rules just incase you the already provided rules are not enough.


Setting up your enviornment

Download Yeoman to help you generate the eslint plugin boilerplate:

Getting started with custom ESlint rules

Everyone can agree that Eslint is an extremely useful tool for programmers to keep their code looking nice and tidy for others, but sometimes Eslint doesnt provide a specific rule to some developers who are looking for a specific solution. Thankfully Eslint gives you the power to create your own custom rules just incase you the already provided rules are not enough.


Setting up your enviornment

Download Yeoman to help you generate the eslint plugin boilerplate:

Getting started with custom ESlint rules

Everyone can agree that Eslint is an extremely useful tool for programmers to keep their code looking nice and tidy for others, but sometimes Eslint doesnt provide a specific rule to some developers who are looking for a specific solution. Thankfully Eslint gives you the power to create your own custom rules just incase you the already provided rules are not enough.


Setting up your enviornment

Download Yeoman to help you generate the eslint plugin boilerplate:

module.exports = {
config: {
// default font size in pixels for all tabs
fontSize: 12,
// font family with optional fallbacks
fontFamily: 'Fira Code Retina',
// terminal cursor background color and opacity (hex, rgb, hsl, hsv, hwb or cmyk)
cursorColor: 'rgba(248,28,229,0.8)',
// Import only the components that we are going to use for security reasons
import * as firebase from 'firebase/app';
import 'firebase/auth';
import 'firebase/database';
// Export your app because you will be using it in other files
export const app = firebase.initializeApp({
apiKey: "",
authDomain: "",
databaseURL: "",
import Vue from 'vue'
import App from './App.vue'
import VueFire from 'vuefire'
import './firebase'
Vue.config.productionTip = false
Vue.use(VueFire)
new Vue({
el: '#app',
<template>
<div>
<h1>Hello World!</h1>
</div>
</template>
<script>
export default {
name: 'app'
}
</script>
<template>
<div>
<h1> Hello! My name is {{ Firstname }} {{ LastName }}</h1>
<h3> Location {{ location }}</h3>
<h1> About me: </h1>
<p>{{ about_me }}</p>
<h1>Projects I have worked on</h1>
<ul>
<script>
import { db, page_data, admin_user } from "./firebase";
export default {
name: "App",
firebase: {
data: {
source: page_data,
readyCallback: function() {
this.loaded = true;
}
# THIS SCRIPT CREATES TEST ACCOUNTS FOR SALESFORCE
# run this with 'python scripts/generate_account_data.py --amount <amount of records to generate>
# Out file: generated_account_data.csv
import csv
from faker import Faker
import random
from account_gen_assets.state_abr import us_state_abbrev
from account_gen_assets.g_cities import city_to_state_dict