Initial commit

.gitignore

@@ -0,0 +1,53 @@
+## OS X Finder
+.DS_Store
+
+## Build generated
+build/
+DerivedData
+
+## Various settings
+*.pbxuser
+!default.pbxuser
+*.mode1v3
+!default.mode1v3
+*.mode2v3
+!default.mode2v3
+*.perspectivev3
+!default.perspectivev3
+xcuserdata
+
+## Other
+*.xccheckout
+*.moved-aside
+*.xcuserstate
+*.xcscmblueprint
+
+## Obj-C/Swift specific
+*.hmap
+*.ipa
+
+## Playgrounds
+timeline.xctimeline
+playground.xcworkspace
+
+# Swift Package Manager
+#
+# Add this line if you want to avoid checking in source code from Swift Package Manager dependencies.
+# Packages/
+.build/
+
+# CocoaPods
+#
+# We recommend against adding the Pods directory to your .gitignore. However
+# you should judge for yourself, the pros and cons are mentioned at:
+# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
+#
+Pods/
+
+# Carthage
+#
+# Add this line if you want to avoid checking in source code from Carthage dependencies.
+Carthage/Checkouts
+
+Carthage/Build
+Frameworks/

.travis.yml

@@ -0,0 +1,13 @@
+language: objective-c
+osx_image: xcode7.2
+
+before_install:
+- brew update
+- brew outdated carthage || brew upgrade carthage
+- if brew outdated | grep -qx xctool; then brew upgrade xctool; fi
+- carthage update --platform iOS
+- gem install xcpretty --no-rdoc --no-ri --no-document --quiet
+
+script:
+- xctool clean build -project CreditCardRow.xcodeproj -scheme CreditCardRow -sdk iphonesimulator
+- xctool test -project CreditCardRow.xcodeproj -scheme CreditCardRow -sdk iphonesimulator

CHANGELOG.md

@@ -0,0 +1,9 @@
+# Change Log
+All notable changes to CreditCardRow will be documented in this file.
+
+### [1.0.0](https://github.com/xmartlabs/CreditCardRow/releases/tag/1.0.0)
+<!-- Released on 2016-01-20. -->
+
+* This is the initial version.
+
+[xmartlabs]: https://xmartlabs.com

CONTRIBUTING.md

@@ -0,0 +1,61 @@
+Contributing Guidelines
+--------------------------------------------------
+
+This document provides general guidelines about how to contribute to the project. Keep in mind these important things before you start contributing.
+
+### Asking Questions
+
+We do not use github issues for general library support. We think this questions should be posted on stack overflow using [CreditCardRow](http://http://stackoverflow.com/questions/tagged/CreditCardRow) tag.
+
+### Reporting issues
+
+* Use [github issues](https://github.com/xmartlabs/CreditCardRow/issues) to report a bug.
+* Before creating a new issue:
+  * Make sure you are using the [latest release](https://github.com/xmartlabs/CreditCardRow/releases).
+  * Check if the issue was [already reported or fixed](https://github.com/xmartlabs/CreditCardRow/issues?utf8=%E2%9C%93&q=is%3Aissue). Notice that it may not be released yet.
+  * If you found a match add a brief comment "I have the same problem" or "+1". This helps prioritize the issues addressing the most common and critical first. If possible add additional information to help us reproduce and fix the issue. Please use your best judgement.    
+* Reporting issues:
+  * Please include the following information to help maintainers to fix the problem faster:
+    * Xcode version you are using.
+    * iOS version you are targeting.
+    * Full Xcode console output of stack trace or code compilation error.
+    * Any other additional detail you think it would be useful to understand and solve the problem.
+
+
+### Pull requests
+
+The easiest way to start contributing is searching open issues by `help wanted` tag. We also add a `difficulty` tag (difficulty: easy, difficulty: moderate, difficulty: hard) in order to give an idea of how complex it can be to implement the feature according maintainers project experience.
+
+* Add test coverage to the feature or fix. We only accept new feature pull requests that have related test coverage. This allows us to keep the library stable as we move forward.
+* Remember to document the new feature. We do not accept new feature pull requests without its associated documentation.
+* In case of a new feature please update the example project showing the feature.
+* Please only one fix or feature per pull request. This will increase the chances your feature will be merged.
+
+
+###### Suggested git workflow to contribute
+
+1. Fork the CreditCardRow repository.
+2. Clone your forked project into your developer machine: `git clone [email protected]:<your-github-username>/CreditCardRow.git`
+3. Add the original project repo as upstream repository in your forked project: `git remote add upstream [email protected]:xmartlabs/CreditCardRow.git`
+4. Before starting a new feature make sure your forked master branch is synchronized upstream master branch. Considering you do not mere your pull request into master you can run: `git checkout master` and then `git pull upstream master`. Optionally `git push origin master`.
+5. Create a new branch. Note that the starting point is the upstream master branch HEAD. `git checkout -b my-feature-name`
+6. Stage all your changes `git add .` and commit them `git commit -m "Your commit message"`
+7. Make sure your branch is up to date with upstream master, `git pull --rebase upstream master`, resolve conflicts if necessary. This will move your commit to the top of git stack.
+8. Squash your commits into one commit. `git rebase -i HEAD~6` considering you did 6 commits.
+9. Push your branch into your forked remote repository.
+10. Create a new pull request adding any useful comment.
+
+
+###### Code style and conventions
+
+We try to follow our [swift style guide](https://github.com/xmartlabs/Swift-Style-Guide). Following it is not strictly necessary to contribute and to have a pull request accepted but project maintainers try to follow it. We would love to hear your ideas to improve our code style and conventions. Feel free to contribute.
+
+
+### Feature proposal
+
+We would love to hear your ideas and make a discussions about it.
+
+* Use github issues to make feature proposals.
+* We use `type: feature request` label to mark all [feature request issues](https://github.com/xmartlabs/CreditCardRow/labels/type%3A%20feature%20request).
+* Before submitting your proposal make sure there is no similar feature request. If you found a match feel free to join the discussion or just add a brief "+1" if you think the feature is worth implementing.
+* Be as specific as possible providing a precise explanation of feature request so anyone can understand the problem and the benefits of solving it.

Cartfile

@@ -0,0 +1,2 @@
+github "xmartlabs/Eureka"
+github "MaxKramer/SwiftLuhn"

Cartfile.resolved

@@ -0,0 +1,2 @@
+github "xmartlabs/Eureka" "1.7.0"
+github "MaxKramer/SwiftLuhn" "0.1.1"

Carthage/Checkouts/Nimble/.gitignore

@@ -0,0 +1,19 @@
+.DS_Store
+xcuserdata/
+build/
+.idea
+DerivedData/
+Nimble.framework.zip
+
+# Carthage
+#
+# Add this line if you want to avoid checking in source code from Carthage dependencies.
+# Carthage/Checkouts
+
+Carthage/Build
+
+# Swift Package Manager
+#
+# Add this line if you want to avoid checking in source code from Swift Package Manager dependencies.
+# Packages/
+.build/

Carthage/Checkouts/Nimble/.ruby-version

@@ -0,0 +1 @@
+system

Carthage/Checkouts/Nimble/.swift-version

@@ -0,0 +1 @@
+DEVELOPMENT-SNAPSHOT-2016-02-25-a

Carthage/Checkouts/Nimble/.travis.yml

@@ -0,0 +1,33 @@
+osx_image: xcode7.3
+language: generic
+matrix:
+  include:
+    - os: osx
+      sudo: required
+      env: TYPE=podspec
+    - os: osx
+      env: NIMBLE_RUNTIME_IOS_SDK_VERSION=9.0 TYPE=ios
+    - os: osx
+      env: NIMBLE_RUNTIME_TVOS_SDK_VERSION=9.0 TYPE=tvos
+    - os: osx
+      env: NIMBLE_RUNTIME_OSX_SDK_VERSION=10.10 TYPE=osx
+    - os: osx
+      env: TYPE=swiftpm
+    - os: osx
+      env: NIMBLE_RUNTIME_IOS_SDK_VERSION=10.0 TYPE=ios
+      osx_image: xcode8
+    - os: osx
+      env: NIMBLE_RUNTIME_TVOS_SDK_VERSION=10.0 TYPE=tvos
+      osx_image: xcode8
+    - os: osx
+      env: NIMBLE_RUNTIME_OSX_SDK_VERSION=10.12 TYPE=osx
+      osx_image: xcode8
+    - os: linux
+      dist: trusty
+      sudo: required
+      env: TYPE=swiftpm
+install:
+  - if [[ "$TYPE" == "swiftpm" ]]; then eval "$(curl -sL https://gist.githubusercontent.com/kylef/5c0475ff02b7c7671d2a/raw/02090c7ede5a637b76e6df1710e83cd0bbe7dcdf/swiftenv-install.sh)"; fi
+  - if [[ "$TYPE" == "podspec" ]]; then sudo gem install bundler; bundle install; fi
+script:
+  - ./test $TYPE

Carthage/Checkouts/Nimble/CONTRIBUTING.md

@@ -0,0 +1,112 @@
+<!-- START doctoc generated TOC please keep comment here to allow auto update -->
+<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
+
+- [Welcome to Nimble!](#welcome-to-nimble!)
+  - [Reporting Bugs](#reporting-bugs)
+  - [Building the Project](#building-the-project)
+  - [Pull Requests](#pull-requests)
+    - [Style Conventions](#style-conventions)
+  - [Core Members](#core-members)
+    - [Code of Conduct](#code-of-conduct)
+
+<!-- END doctoc generated TOC please keep comment here to allow auto update -->
+
+# Welcome to Nimble!
+
+We're building a testing framework for a new generation of Swift and
+Objective-C developers.
+
+Nimble should be easy to use and easy to maintain. Let's keep things
+simple and well-tested.
+
+**tl;dr:** If you've added a file to the project, make sure it's
+included in both the OS X and iOS targets.
+
+## Reporting Bugs
+
+Nothing is off-limits. If you're having a problem, we want to hear about
+it.
+
+- See a crash? File an issue.
+- Code isn't compiling, but you don't know why? Sounds like you should
+  submit a new issue, bud.
+- Went to the kitchen, only to forget why you went in the first place?
+  Better submit an issue.
+
+Be sure to include in your issue:
+
+- Your Xcode version (eg - Xcode 7.0.1 7A1001)
+- Your version of Nimble (eg - v2.0.0 or git sha `20a3f3b4e63cc8d97c92c4164bf36f2a2c9a6e1b`)
+- What are the steps to reproduce this issue?
+- What platform are you using? (eg - OS X, iOS, watchOS, tvOS)
+- If the problem is on a UI Testing Bundle, Unit Testing Bundle, or some other target configuration
+- Are you using carthage or cocoapods?
+
+## Building the Project
+
+- Use `Nimble.xcodeproj` to work on Nimble.
+
+## Pull Requests
+
+- Nothing is trivial. Submit pull requests for anything: typos,
+  whitespace, you name it.
+- Not all pull requests will be merged, but all will be acknowledged. If
+  no one has provided feedback on your request, ping one of the owners
+  by name.
+- Make sure your pull request includes any necessary updates to the
+  README or other documentation.
+- Be sure the unit tests for both the OS X and iOS targets of Nimble
+  before submitting your pull request. You can run all the OS X & iOS unit
+  tests using `./test`.
+- If you've added a file to the project, make sure it's included in both
+  the OS X and iOS targets.
+- The `master` branch will always support the stable Xcode version. Other
+  branches will point to their corresponding versions they support.
+- If you're making a configuration change, make sure to edit both the xcode
+  project and the podspec file.
+
+### Style Conventions
+
+- Indent using 4 spaces.
+- Keep lines 100 characters or shorter. Break long statements into
+  shorter ones over multiple lines.
+- In Objective-C, use `#pragma mark -` to mark public, internal,
+  protocol, and superclass methods.
+
+## Core Members
+
+If a few of your pull requests have been merged, and you'd like a
+controlling stake in the project, file an issue asking for write access
+to the repository.
+
+### Code of Conduct
+
+Your conduct as a core member is your own responsibility, but here are
+some "ground rules":
+
+- Feel free to push whatever you want to master, and (if you have
+  ownership permissions) to create any repositories you'd like.
+
+  Ideally, however, all changes should be submitted as GitHub pull
+  requests. No one should merge their own pull request, unless no
+  other core members respond for at least a few days.
+
+  If you'd like to create a new repository, it'd be nice if you created
+  a GitHub issue and gathered some feedback first.
+
+- It'd be awesome if you could review, provide feedback on, and close
+  issues or pull requests submitted to the project. Please provide kind,
+  constructive feedback. Please don't be sarcastic or snarky.
+
+### Creating a Release
+
+The process is relatively straight forward, but here's is a useful checklist for tagging:
+
+- Look at changes from the previously tagged release and write release notes: `git log v0.4.0...HEAD`
+- Run the release script: `./script/release A.B.C release-notes-file`
+- The script will prompt you to create a new [GitHub release](https://github.com/Quick/Nimble/releases).
+  - Use the same release notes you created for the tag, but tweak up formatting for GitHub.
+- Update [Quick](https://github.com/Quick/Quick)
+  - Update Quick's submodule reference to the newly released Nimble version
+  - Update Nimble version in `README.md` and Documentation in [Quick](https://github.com/Quick/Quick) if it's not a patch version update.
+- Announce!

Carthage/Checkouts/Nimble/Gemfile

@@ -0,0 +1,4 @@
+# A sample Gemfile
+source "https://rubygems.org"
+
+gem 'cocoapods'

Carthage/Checkouts/Nimble/Gemfile.lock

@@ -0,0 +1,63 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (4.2.6)
+      i18n (~> 0.7)
+      json (~> 1.7, >= 1.7.7)
+      minitest (~> 5.1)
+      thread_safe (~> 0.3, >= 0.3.4)
+      tzinfo (~> 1.1)
+    claide (0.9.1)
+    cocoapods (0.39.0)
+      activesupport (>= 4.0.2)
+      claide (~> 0.9.1)
+      cocoapods-core (= 0.39.0)
+      cocoapods-downloader (~> 0.9.3)
+      cocoapods-plugins (~> 0.4.2)
+      cocoapods-search (~> 0.1.0)
+      cocoapods-stats (~> 0.6.2)
+      cocoapods-trunk (~> 0.6.4)
+      cocoapods-try (~> 0.5.1)
+      colored (~> 1.2)
+      escape (~> 0.0.4)
+      molinillo (~> 0.4.0)
+      nap (~> 1.0)
+      xcodeproj (~> 0.28.2)
+    cocoapods-core (0.39.0)
+      activesupport (>= 4.0.2)
+      fuzzy_match (~> 2.0.4)
+      nap (~> 1.0)
+    cocoapods-downloader (0.9.3)
+    cocoapods-plugins (0.4.2)
+      nap
+    cocoapods-search (0.1.0)
+    cocoapods-stats (0.6.2)
+    cocoapods-trunk (0.6.4)
+      nap (>= 0.8, < 2.0)
+      netrc (= 0.7.8)
+    cocoapods-try (0.5.1)
+    colored (1.2)
+    escape (0.0.4)
+    fuzzy_match (2.0.4)
+    i18n (0.7.0)
+    json (1.8.3)
+    minitest (5.8.4)
+    molinillo (0.4.4)
+    nap (1.1.0)
+    netrc (0.7.8)
+    thread_safe (0.3.5)
+    tzinfo (1.2.2)
+      thread_safe (~> 0.1)
+    xcodeproj (0.28.2)
+      activesupport (>= 3)
+      claide (~> 0.9.1)
+      colored (~> 1.2)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  cocoapods
+
+BUNDLED WITH
+   1.11.2