xcode-yamlizer 0.0.1 → 0.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/lib/xcode-yamlizer/version.rb +1 -1
- data/xcode-yamlizer.gemspec +0 -1
- metadata +2 -24
data/xcode-yamlizer.gemspec
CHANGED
@@ -8,7 +8,6 @@ Gem::Specification.new do |gem|
|
|
8
8
|
gem.version = XcodeYamlizer::VERSION
|
9
9
|
gem.authors = ["Sergey Klimov"]
|
10
10
|
gem.email = ["sergey.v.klimov@gmail.com"]
|
11
|
-
gem.description = IO.read("README.md")
|
12
11
|
gem.summary = %q{Set of git hooks to store YAML files instead of Xcode projects and nibs in repo}
|
13
12
|
gem.homepage = "https://github.com/darvin/xcode-yamlizer"
|
14
13
|
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: xcode-yamlizer
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.2
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -107,29 +107,7 @@ dependencies:
|
|
107
107
|
- - ! '>='
|
108
108
|
- !ruby/object:Gem::Version
|
109
109
|
version: '0'
|
110
|
-
description:
|
111
|
-
\n[formats](http://stackoverflow.com/questions/4022362/merging-xcode-project-files)\n[are](https://discussions.apple.com/thread/3081125?start=0&tstart=0)
|
112
|
-
\n[shitty](http://stackoverflow.com/questions/10552082/finding-the-error-in-xcodes-project-pbxproj-after-merge)
|
113
|
-
\nThey are pain to merge and are impossible to read. YAML is pretty.\n\nImagine
|
114
|
-
a brave new world with XCode's `nib`s, model files, storyboards,\nproject files
|
115
|
-
- all in YAML. Thats what that project do!\n\nYou can see how pretty it looks on
|
116
|
-
Github in this sample repo.\n\n\n## Installation\n\nInstall XcodeYamlizer with:\n\n
|
117
|
-
\ $ gem install xcode-yamlizer\n\n## Usage\n\n### Git hooks\n\nThe best and recommended
|
118
|
-
way is to install `pre-commit` and `post-merge` hook.\nYou can do that from your
|
119
|
-
project's working directory:\n\n $ xcode-yamlize install\n\nThen, before commit,
|
120
|
-
`pre-commit` hook will:\n\n # find all obscure `.xib`s, `.xcdatamodel`s, project
|
121
|
-
files, etc.\n # create appropriate YAML files with the same name + `.yaml` extension\n
|
122
|
-
\ # add them to commit (if necessary)\n # add all obscure files to `.gitignore`
|
123
|
-
(if necessary)\n # remove all obscure files from git (if necessary) (but will
|
124
|
-
leave them be in file system)\n\nAfter merge, `post-merge` hook will:\n\n # copy
|
125
|
-
all obscure files to the same name + `~` postfix\n # overrite all obscure files
|
126
|
-
from the version controlled `yaml`es.\n\n### Standalone\n\n```\n$ xcode-yamlizer\noptions:\n
|
127
|
-
-input (-i) convert file (autodetects direction)\n -dir (-d) convert directory
|
128
|
-
(default direction - from XCode to YAML)\n -to_xcode direction: from YAML to
|
129
|
-
XCode format\n -verbose verbose mode\n -help (-h) show help\n```\n\n## Contributing\n\n1.
|
130
|
-
Fork it\n2. Create your feature branch (`git checkout -b my-new-feature`)\n3. Commit
|
131
|
-
your changes (`git commit -am 'Add some feature'`)\n4. Push to the branch (`git
|
132
|
-
push origin my-new-feature`)\n5. Create new Pull Request\n"
|
110
|
+
description:
|
133
111
|
email:
|
134
112
|
- sergey.v.klimov@gmail.com
|
135
113
|
executables:
|