rom-rb/rom-mapper Rom mapper

Standalone ROM mappers

#14 (all)
Ruby (change)
6 seconds
over 4 years ago

Here you can see the build history of your project.

In case the documentation changed, it is shown here.

#14 Merge pull request #37 from astupka/astupka/union_value_copy [5cc3714c] 6 seconds over 4 years ago
#13 Merge pull request #36 from astupka/master [386ad704] 6 seconds over 4 years ago
Show 1 low priority object ...
3 builds omitted (no changes to documentation).
#9 Merge pull request #29 from drinks/implement-copy-keys [23bcecc9] 22 seconds almost 5 years ago
Show 2 low priority objects ...
1 build omitted (no changes to documentation).
#7 v0.3.0.bet... 22 seconds almost 5 years ago
#6 Run specs on jruby-9000 [9bc5e0a2] 18 seconds almost 5 years ago
Show 2 low priority objects ...
1 build omitted (no changes to documentation).
#4 Merge pull request #27 from rom-rb/feature/mapper-binding [e6d889fb] 15 seconds almost 5 years ago
Show 1 low priority object ...
2 builds omitted (no changes to documentation).
#1 Update README [5d4f43a7] 8 seconds about 5 years ago
U
ROM Ne
A
ROM::Processor Ne
Show 164 low priority objects ...

Let's raise the visibility of documentation in Open Source!

This page is for rom-rb/rom-mapper and is part of a project called "Inch CI", showing documentation measurements provided by Inch. Inch CI also provides a badge: (not counting low priority objects)

Can I have my own badges?

Sure! To get the badge for the project you are looking at, just click the badge next to the project name.

To register another project with Inch CI, just enter your username/repo on the homepage or sign in with GitHub!

Can I tell Inch which files to evaluate?

No problemo! Learn how ...

Can I configure a webhook for continuous integration?

Of course! Learn how ...

What is the goal of this?

I really think that posting badges for documentation in READMEs will benefit you (because people can see that your project is well documented) and our community in general by improving the visibility of documentation.

Let's start a discussion, let's raise the visibility of documentation, let's talk.

Suggestions, feedback, critique: Hit me up on Twitter or via issue.