faaezahmd

console.log("Before the first file is read.");
hypotheticalFileGetContents("sample.txt", function(fileContents){
	// fileContents now contains the file contents, this function is only called when the file read in the background has finished
	console.log("After the first file has completed reading.");
});

// You've now told it to start the first read, but it won't 'block' your script execution. It will do the read in the background, and immediately move on with the rest of your code.

console.log("Before the second file is read.");
hypotheticalFileGetContents("sample2.txt", function(fileContents){

faaezahmd

// Lets us create Taxonomy for Custom Post Type
add_action( 'init', 'jobs_custom_taxonomy', 0 );
 
//create a custom taxonomy name it "type" for your posts
function jobs_custom_taxonomy() {
  $labels = array(
    'name' => _x( 'Types', 'taxonomy general name' ),
    'singular_name' => _x( 'Type', 'taxonomy singular name' ),
    'search_items' =>  __( 'Search Types' ),
    'all_items' => __( 'All Types' ),

faaezahmd

Git Branch Merging Best Practices

1. After you've selected a feature to work on, create a branch in your local repo to build it in.
   • $ git checkout -b calaway/short_description_of_feature
2. Implement the requested feature, make sure all tests are passing, and commit all changes in the new branch.
3. Checkout the master branch locally.
   • $ git checkout master
4. Pull down the master branch from GitHub to get the most up to date changes from others. If you practice git workflow as described here you should never have a merge conflict at this step.
   • $ git pull origin master
5. Make sure all tests are passing on master and then checkout your new branch.

• $ git checkout calaway/short_description_of_feature

faaezahmd

const COUNTRY_CODES = [
  {
    name: 'Afghanistan +93',
    id: '+93',
    code: 'AF',
  },
  {
    name: 'Aland Islands +358',
    id: '+358',
    code: 'AX',