Commits on Feb 17, 2017
  1. Clarify that questions should be good questions

    State some of the elements from
    greggles committed with croaky Feb 17, 2017
Commits on Feb 10, 2017
  1. Remove broken Readability link

    The better option would be to replace the readability link
    with the correct one,
    but I don't know which one is that.
    budmc29 committed with croaky Feb 10, 2017
Commits on Feb 9, 2017
  1. Update old blog link

    tysongach committed Feb 7, 2017
Commits on Feb 8, 2017
  1. Add best practice for documenting CSS architecture

    - Each project is unique and our guides on front-end development
    purposefully do not prescribe a specific way to structure and
    organize CSS.
    - Documenting how the project's CSS is structured and organized allows
    for a shared understanding, making it easier to contribute to
    and review.
    tysongach committed Jan 23, 2017
Commits on Jan 28, 2017
  1. Remove HTML best practices

    These two guides were introduced in 2360fac.
    - "Don't use a reset button for forms." feels like too strong of a statement and
    casts a wide net.
    - It is unclear why these are best practices.
    - These guidelines are highly dependent on the situation.
    - They lack contextual information on when these best practices should
    be adhered to or broken.
    tysongach committed Jan 23, 2017
  2. Drop IE10 from browser support best practice

    Can I Use (with data from StatCounter) reports that global IE10 usage has
    dropped to 0.24%:
    tysongach committed Jan 23, 2017
  3. Clarify sass-rails asset helpers best practice

    These asset helpers are specific to sass-rails. Not every project is
    built on Ruby on Rails and sass-rails.
    tysongach committed Jan 23, 2017
  4. Move CSS overflow best practice

    This has nothing to do with Sass and everything to do with CSS.
    tysongach committed Jan 23, 2017
Commits on Jan 27, 2017
  1. Expand "security" to physical + vulnerabilities

    Based on similar sections seen in compliance questionnaires,
    re-title existing sections and add new sections:
    * Secure Employee Access and Communication
    * Application Security: Transmitting Information
    * Application Security: Storing Information
    * Physical Security
    * Handling Vulnerabilities: Reporting
    * Handling Vulnerabilities: Reviewing, Logging and Following Up
    Extract the new sections from internal handbook.
    croaky committed Jan 27, 2017
Commits on Jan 23, 2017
  1. Disable Style/AlignParameters in Rubocop

    This has Rubocop match the change made in
    mike-burns committed Jan 23, 2017
Commits on Jan 12, 2017
  1. Change DeprecatedHashMethods to PreferredHashMethods

    This change was officially made in June, and raises a warning when
    running rubocop.
    "Warning: unrecognized cop Style/DeprecatedHashMethods"
    yakschuss committed with geoffharcourt Oct 30, 2016
Commits on Jan 4, 2017
  1. Add ESLint Hound configuration

    Before, Hound had its own default ESLint configuration. We are moving
    these configurations into specific organisations. Added a
    thoughtbot-specific Hound configuration for ES6 files.
    purinkle committed Jan 4, 2017
  2. Add Haml Hound configuration

    Before, Hound had its own default Haml configuration. We are moving
    these configurations into specific organisations. Added a
    thoughtbot-specific Hound configuration for Haml files.
    purinkle committed Jan 4, 2017
Commits on Dec 21, 2016
  1. Remove weird comment about attractiveness

    This is out of place and borderline inappropriate. There's really no
    need to reference physical appearance here, so how about we just don't.
    gfontenot committed Dec 21, 2016
Commits on Dec 16, 2016
  1. Convert jscsrc config to eslint

    The JSCSRC project was absorbed into ESLint. I ran our configuration of
    JSCSRC through polyjuice and to convert it.
    derekprior committed Dec 16, 2016
Commits on Oct 27, 2016
  1. Update link in README

    The `/community` link now redirects to `/tools`.
    The home page may be more relevant to guides readers.
    toomey8 committed with croaky Oct 27, 2016
Commits on Sep 30, 2016
Commits on Sep 14, 2016
  1. [Rubocop] Disable FrozenStringLiteralComment

    RuboCop, somewhat recently, added the
    [Style/FrozenStringLiteralComment][1] cop, which enforces the presence
    of the `# frozen_string_literal: true` pragma at the top of every file,
    when running in Ruby 2.3 mode. Hound recently [configured][2] RuboCop to
    run in Ruby 2.3 mode by default. This means Hound will now comment on
    any Ruby file touched in a PR that doesn't have the pragma, with:
    > Missing frozen string literal comment.
    This is intended to prepare code bases for Ruby 3.0, where strings will
    be frozen by default. In practice, I find Hound making these comments to
    be quite annoying, and I have disabled it on my current project.
    It seems we can disable the cop, or start putting the pragma at the top
    of all our files. The former seems easier so it's my pick.
    [1]: bbatsov/rubocop#2542
    [2]: houndci/linters#65
    thorncp committed Sep 8, 2016
Commits on Sep 12, 2016
  1. Fix links in the file (#447)

    * Fix links in the file
    joseVFernandez committed with iwz Sep 12, 2016
Commits on Aug 30, 2016
Commits on Aug 23, 2016
  1. Add coffeescript config file + update hound config

    Now that this repo is the owner configuration repo for all thoughtbot
    repositories in Hound it needs to explicitly define a set of
    coffeescript styles.
     - Copy over `coffeelint.json` from Hound repo
     - Configure coffeescript in `.hound.yml` to be enabled and to point at
    jcmorrow committed Jul 22, 2016
Commits on Jul 28, 2016
  1. Disable UrlFormat linter

    This linter is a bit too generalized to have enabled by default.
    For example, on the thoughtbot blog we use a CDN for images, so having
    an external domain with protocol makes sense, but this linter will throw
    a warning.
    tysongach committed Jul 28, 2016
Commits on Jul 27, 2016
Commits on Jul 22, 2016
  1. Trailing comma in Sass maps

    This makes for cleaner diffs when adding to or
    removing from the map.
    This also aligns with our JavaScript guideline.
    tysongach committed Jul 19, 2016
Commits on Jul 19, 2016
Commits on Jun 24, 2016
  1. Update rubocop config to match hound settings

    From now on hound will use this repository's configuration for all
    thoughbot repos. There were a few settings that differed between the
    two, so I'm adding the missing configs to make this look just like
    hound's default thoughtbot configuration.
    jcmorrow committed Jun 24, 2016
Commits on Jun 6, 2016
Commits on May 27, 2016
  1. Add Swift guideline recommending weak references are evaluated once

    If a weak reference is evaluated multiple times within the same scope,
    it's technically possible for the reference to change between `nil` and
    non-`nil` between references. In order to ensure that valid references
    remain valid for the entire scope, recommend that weak references are
    evaluated only once.
    sharplet committed Mar 4, 2016
  2. Prefer protocol conformance to object inheritance

    Protocol conformance in Swift 2+ is a much more powerful form of
    polymorphism than object inheritance and so should be the preferred
    method. Among other things, using protocols means that you don't need to
    care about the kind of object (struct, enum, or class), which puts way
    fewer restrictions on your larger project architecture decisions.
    Conversely, since object inheritance can only be achieved with classes,
    they force you to make certain decisions about your application
    architecture that might have adverse side effects.
    gfontenot committed Feb 12, 2016
  3. Put remote devs on equal footing for code review

    Instead of promoting in-person communication, we can promote synchronous
    communication. This matches the intent without ignoring the increasing
    chance that a developer is remote.
    robwierzbowski committed with mike-burns May 9, 2016
Commits on Apr 29, 2016
  1. Prefer private for non-public accessors

    We added a preference for `protected` over `private` for non-public
    accessors in [#190]. The primary motivation was because Ruby emitted
    warnings when declaring private attributes.
    In Ruby versions 2.3.0 and greater, Ruby no longer warns about private
    attributes, so there's no longer a need to use `protected` for them.
      [#190]: #190
    bernerdschaefer committed Mar 23, 2016