- 🙅♀️ Code formatting
- Does it use the correct indentation method?
- 🙅♀️ Code style
- Does it respect our style guidelines?
- 🙅♀️ Name formatting
- Does it use camelcase vs underscore vs ...?
- 🙅♀️ Test coverage
- Do the tests cover the majority of the code written?
[user] | |
name = emarchak | |
email = | |
[core] | |
excludesfile = /Users/emarchak/.gitignore_global | |
commitGraph = true | |
[alias] | |
trash = "!git add -A && git commit -m trash && git reset --hard HEAD^" | |
killall = "!git branch | grep -v 'master' | xargs git branch -D" | |
reset-branch = "!git reset --soft HEAD~$(git rev-list --count HEAD ^origin/master)" |
<nav role="navigation" aria-labelledby="pagination-heading"> | |
<h4 id="pagination-heading" class="visually-hidden">Pagination</h4> | |
<ul> | |
<li> | |
<a href="?page=0" rel="first"> | |
First<span class="visually-hidden"> page</span> | |
</a> | |
</li> | |
<li> | |
<a href="?page=1" rel="prev"> |
#!/bin/bash | |
# USAGE | |
# Run this script as given. | |
# | |
# $ bash rename.sh [ relative/path/to/csvfile.csv ] | |
# Set from args | |
CSV="$1" |
A strong benefit of having a Jenkins server is to allow the team to test how the application behaves, and understand regressions before they are released to production. This is done through the Jenkins server running Behat tests, which are behaviour tests written alongside the codebase. They are able to be run in browserstack, so we can simulate multiple advisors running through the system at any given time.
Using Jenkins and automated testing also allows us to practice Behaviour Driven Development (BDD), which is an agile development methodology that is a derivation of Test Driven Development. Myplanet uses BDD in the majority of it's projects, as it improves the quality of code while also helping us communicate the business value of a story.
BDD improves upon the quality assurance practices of Test Driven Development by incorporating the business value into the tests. The team is required to understand why we're implementing functionality before we define
<?php | |
function g*********d_header_update_7001(&$sandbox){ | |
$theme_settings = variable_get('theme_eli_settings', array()); | |
$theme_settings['alpha_region_top_nav_zone'] = 'menu'; | |
variable_set('theme_eli_settings', $theme_settings); | |
} |
<?php | |
date_default_timezone_set('America/New_York'); | |
$current = new DateTime('NOW'); | |
$september = strtotime('1 October ' . $current->format('Y')); | |
if ($current->format('U') > $september) { | |
print 'Wake up, Greenday.'; | |
} |
I had a really good discussion with Derek Featherstone about accessible modal dialogs. He suggested going with jQuery UI's Dialog, but with the following steps:
-
Inject the content right beside the activating button, this allows keyboard users to quickly get inside the modal.
-
Make sure the activating item is an anchor tag, and targets the id of the modal div, so the focus is placed on it.
-
Give the modal div a tabindex="-1" so that it can be focused via the link, but not accidentally tabbed into.
-
Give modal div an ARIA tag of aria-labelledby="ID", where ID is the id of the header tag contained on the modal div.
/** | |
* The first commented line is your dabblet’s title | |
*/ | |
background: #f06; | |
background: linear-gradient(45deg, #f06, yellow); | |
min-height:100%; |