Skip to content
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.

Merging v0.2.0 into master! #13

Merged
merged 22 commits into from
Jul 7, 2015
Merged

Merging v0.2.0 into master! #13

merged 22 commits into from
Jul 7, 2015

Conversation

owensd
Copy link
Owner

@owensd owensd commented Jul 7, 2015

The big changes in this version are:

  1. Support for #! in your scripts.
  2. Support for nested folders within your script; everything just gets compiled together happily.
  3. Some basic tests to catch regressions earlier.

This version was essentially a rewrite and restructuring, of what was essentially, a proof-of-concept implementation. Much of the boilerplate was removed and things were streamlined in the source. The fundamental difference between v0.1 and v0.2 is that v0.2 actually creates a proper binary to run instead of just merging all of the scripts into a single file and running it through the REPL.

owensd added 22 commits July 6, 2015 09:49
Adds support for nested directories (issue #1).
Added nested folder sample.
…ead of also allowing a specific swift file to be mentioned.
Major cleanup of the tool’s API surface; everything has been
streamlined to a function-based interface.
Fixed the issue with streaming output to stdout.
Fixed a bug with relative paths.
Added some of the tests (missing CocoaPods and Carthage tests).
… work reliably. Falling back to the previous behavior, which is not ideal, but at least it's robust. I'll look at this for v0.3.0.

The `filesAtPath()` needed to filter out the Carthage and CocoaPods folders and not try to build that content into the script tool... might be a good thing.
owensd added a commit that referenced this pull request Jul 7, 2015
Merging v0.2.0 into master!
@owensd owensd merged commit 034ecf1 into master Jul 7, 2015
@owensd owensd deleted the v0.2.0-dev branch July 7, 2015 18:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant