rubygems
/
inflecto
1
0
Fork 0
Code Packages Releases Activity
Inflector for ruby https://github.com/mbj/inflecto
116 Commits 2 Branches 0 Tags 246 KiB
Go to file
Alex Kotov 0c266678c8
Sign the gem 		2022-11-15 17:17:13 +04:00
config Make mutant happy 2016-07-19 20:12:30 +03:00
lib Fix doc example 2016-08-11 01:25:22 +03:00
spec Make mutant happy 2016-07-19 20:12:30 +03:00
.gitignore Update .gitignore to include more common exclusions 2013-03-17 19:36:27 -07:00
.rspec Add class method specs extracted from extlib 2012-10-15 19:53:29 +02:00
.rvmrc Add base rvmrc 2013-03-17 19:39:42 -07:00
.travis.yml Drop 1.9.2 and bump version 2014-11-27 15:15:46 +02:00
Changelog.md Prepare Changelog 2013-01-20 17:30:24 +01:00
Gemfile Remove duplicate gem dependency from Gemfile 2016-10-20 05:21:49 +03:00
Guardfile Update devtools, add travis.yml and cleanup specs 2012-12-12 18:16:59 +01:00
LICENSE Fix attribution in LICENS and README 2012-12-12 19:48:29 +01:00
README.md Fix contributors 2013-05-28 17:02:06 +02:00
Rakefile Update Rakefile to use recent devtools API 2013-03-17 19:35:52 -07:00
TODO Add notes about missing authorship and license 2012-11-06 19:57:45 +01:00
inflecto.gemspec Sign the gem 2022-11-15 17:17:13 +04:00

README.md

inflecto

Gem Version Build Status Dependency Status Code Climate Coverage Status

This is a standalone inflector ripped out from dm-core The dm-core inflector originated from extlib The extlib inflecto originated from active_support

Installation

Install the gem inflecto via your preferred method.

Examples

Soon.

Credits

The rails, merb & datamapper team

The current maintainer is Markus Schirp (mbj) with help from indrekj.

Contributing

  • If you want your code merged into the mainline, please discuss the proposed changes with me before doing any work on it. This library is still in early development, and the direction it is going may not always be clear. Some features may not be appropriate yet, may need to be deferred until later when the foundation for them is laid, or may be more applicable in a plugin.
  • Fork the project.
  • Make your feature addition or bug fix.
  • Add specs for it. This is important so I don't break it in a future version unintentionally. Tests must cover all branches within the code, and code must be fully covered.
  • Commit, do not mess with Rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
  • Run "rake ci". This must pass and not show any regressions in the metrics for the code to be merged.
  • Send me a pull request. Bonus points for topic branches.

License

See LICENSE for details