rajasegar

#!/bin/sh
rm -Rf dist/*
ember build --env=production
mkdir /tmp/ember-aria-accordion
cp -R dist/* /tmp/ember-aria-accordion
git checkout gh-pages
rm -Rf ./*
cp -R /tmp/ember-aria-accordion/* ./
git add .
git commit -m "Publishing docs for $(git describe --tags)"

rajasegar

#!/bin/sh

REPO_NAME=$(sed -n '/name/p' package.json | awk '{print $2}' | sed 's/"//g; s/,//g')
DIST_FOLDER=dist

# Clean up dist folder
rm -Rf $DIST_FOLDER/*

# Run the build
npm run build

rajasegar

/* jshint node : true */
module.exports = [{
  name: 'contacts',
  packages: ['contacts'],
  handledRoutesPatterns: ['/contact'],
  routeNames: ['^contact']
}];

rajasegar

# to describe aliase => $ type rd
# to view list of aliases => $ alias

# https://githowto.com/aliases

# my bash aliases
alias rd='rm -Rf'
alias cx='cp -R'
alias lst='ls -lh'
alias ls='ls -lhGs'

rajasegar

This was a long pending blog post (since 2018) but I wish not to miss the deadline this time. After having worked with Angular for a brief period of 6 months, building websites with jQuery and creating products with Ember, I am so grateful that I have decided to stay with this framework for 4 long years and would still continue to do so. So here are my thoughts or rather the wish list that Ember as a community should solve in the near future.

1. Documentation / easing new developer onboarding

Being an experienced Ember developer myself, on-boarding new and fresh minds from a different background of frameworks into teams that use Ember, has been quite a challenge. Not because it is difficult to learn, but the dots around the documentation need a bit more connectivity. I’m su

rajasegar

tips = ["hello", "world"]

def print_tips
end
    

rajasegar

require 'parser/current'
require 'json'


code = File.read('sample.rb')
ast = Parser::CurrentRuby.parse(code)

#pp ast

@indent = 0

rajasegar

v:1
parser:2.6.3.0
rails:5.2.3
ruby:2.5.5p157

rajasegar

v:1
parser:2.6.3.0
rails:5.2.3
ruby:2.5.5p157

rajasegar

bar.baz();