fixbraces 1.3.0 → 1.3.1

Sign up to get free protection for your applications and to get access to all the features.
data/CHANGELOG.md CHANGED
@@ -1,5 +1,10 @@
1
1
  # Fixbraces Changelog #
2
2
 
3
+ ## 1.3.0 ##
4
+
5
+ - Add the `--dry-run, -d` option to list the files that would change, but make
6
+ no actual corrections.
7
+
3
8
  ## 1.2.0 ##
4
9
  - Error and exit if no file or directory is passed to the script
5
10
  - Print a message and gracefully handle non-existent path or directory
data/README.md CHANGED
@@ -1,11 +1,13 @@
1
1
  # Fixbraces
2
2
 
3
- Make sure that the opening brace for an Objective-C code block is on the same
4
- line.
3
+ A command line app that puts the opening brace for an Objective-C code block on
4
+ the same line as the opening clause.
5
5
 
6
6
  Xcode is inconsistent about the placement of braces for code that it inserts for
7
7
  us. Sometimes it puts the opening braces on the same line, sometimes it puts it
8
- on the next line. I prefer it to be on the opening line.
8
+ on the next line. I prefer it to be on the opening line. This command line app
9
+ makes it easy to change selected source files, or all the files in a folder, or
10
+ even run with the dry-run option to see what files would be changed.
9
11
 
10
12
  ## Installation
11
13
 
@@ -41,11 +43,30 @@ or a number of files:
41
43
 
42
44
  fixbraces aDirectory/*.m
43
45
 
46
+ If you just want to see what files _would_ be changed, then use the `--dry-run`,
47
+ or `-d` option:
48
+
49
+ fixbraces -d .
50
+
44
51
  Run `fixbraces --help` for details.
45
52
 
46
- ## Changelog
53
+ ## Fixbraces Changelog
54
+
55
+ ### 1.3.0
56
+
57
+ - Add the `--dry-run, -d` option to list the files that would change, but make
58
+ no actual corrections.
59
+
60
+ ### 1.2.0
61
+ - Error and exit if no file or directory is passed to the script
62
+ - Print a message and gracefully handle non-existent path or directory
63
+
64
+ ### 1.0.0
65
+ - List the changed files.
66
+
67
+ ### 0.9.0
47
68
 
48
- See the current version of the [Changelog](https://github.com/Abizern/fixbraces/blob/master/CHANGELOG.md) is part of the repository.
69
+ - Initial version.
49
70
 
50
71
  ## Disclaimer
51
72
 
data/fixbraces.gemspec CHANGED
@@ -9,11 +9,16 @@ Gem::Specification.new do |gem|
9
9
  gem.authors = ["Abizer Nasir"]
10
10
  gem.email = ["abizern@junglecandy.com"]
11
11
  gem.description = <<DESC
12
- I prefer my opening braces to be on the same line as the opening clause.
13
- Xcode, and people I collaborate with are inconsistent about the placement
14
- of the opening brace. This corrects it for a file or a directory.
12
+ Xcode is inconsistent about the placement of braces for code that it inserts for
13
+ us. Sometimes it puts the opening braces on the same line, sometimes it puts it
14
+ on the next line. I prefer it to be on the opening line. This command line app
15
+ makes it easy to change selected source files, or all the files in a folder, or
16
+ even run with the dry-run option to see what files would be changed.
15
17
  DESC
16
- gem.summary = "Puts the opening brace on the same line"
18
+ gem.summary = <<SUMM
19
+ A command line app that puts the opening brace for an Objective-C code block on
20
+ the same line as the opening clause.
21
+ SUMM
17
22
  gem.homepage = "http://abizern.org/fixbraces/"
18
23
 
19
24
  gem.files = `git ls-files`.split($/)
@@ -1,3 +1,3 @@
1
1
  module Fixbraces
2
- VERSION = "1.3.0"
2
+ VERSION = "1.3.1"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: fixbraces
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.3.0
4
+ version: 1.3.1
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2013-01-05 00:00:00.000000000 Z
12
+ date: 2013-01-06 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: trollop
@@ -75,11 +75,16 @@ dependencies:
75
75
  - - ~>
76
76
  - !ruby/object:Gem::Version
77
77
  version: '0.5'
78
- description: ! 'I prefer my opening braces to be on the same line as the opening clause.
78
+ description: ! 'Xcode is inconsistent about the placement of braces for code that
79
+ it inserts for
79
80
 
80
- Xcode, and people I collaborate with are inconsistent about the placement
81
+ us. Sometimes it puts the opening braces on the same line, sometimes it puts it
81
82
 
82
- of the opening brace. This corrects it for a file or a directory.
83
+ on the next line. I prefer it to be on the opening line. This command line app
84
+
85
+ makes it easy to change selected source files, or all the files in a folder, or
86
+
87
+ even run with the dry-run option to see what files would be changed.
83
88
 
84
89
  '
85
90
  email:
@@ -178,7 +183,8 @@ rubyforge_project:
178
183
  rubygems_version: 1.8.24
179
184
  signing_key:
180
185
  specification_version: 3
181
- summary: Puts the opening brace on the same line
186
+ summary: A command line app that puts the opening brace for an Objective-C code block
187
+ on the same line as the opening clause.
182
188
  test_files:
183
189
  - features/cli.feature
184
190
  - features/fixbraces.feature