rom-rb/rom Rom

Data mapping and persistence toolkit for Ruby

Refresh
#4 (all)
Ruby (change)
11 seconds
over 5 years ago

Here you can see the build history of your project.

In case the documentation changed, it is shown here.

#4 Simplify Loader.build via new domain param emitter [8277b57e] 11 seconds over 5 years ago
C
ROM::Mapping.build N
B
ROM::Relation#insert N
B
ROM::Session::Relation#new N
B
ROM::Mapper#new_object N
B
ROM::Relation#inject_mapper N
C
ROM::Session::Relation#identity N
C
ROM::Session::Relation#delete N
C
ROM::Session::Relation#track N
C
ROM::Session::Relation#state N
C
ROM::Session::Relation#save N
A
ROM Ne
B
ROM::Environment#mapping Ne
B
ROM::Environment#schema Ne
B
ROM::Schema.build Ne
B
ROM::Environment#[] Ne
C
ROM::Session::Relation#update_attributes Ne
C
ROM::Relation#update Ne
C
ROM::Session#[] Ne
U
Axiom Ne
A
ROM::Session::ObjectNotTrackedError Ne
A
ROM::Session::Environment#[] Ne
A
Axiom::Adapter::DataObjects Ne
A
ROM::Session::Environment Ne
A
Axiom::Adapter#uri_scheme Ne
A
ROM::Session::Relation Ne
A
ROM::Environment.setup Ne
A
ROM::Repository#[]= Ne
A
ROM::Relation#last Ne
A
ROM::Repository#[] Ne
A
ROM::Session#flush Ne
A
ROM::Relation#take Ne
A
ROM::Mapper#model Ne
A
ROM::Relation#one Ne
A
ROM::Environment Ne
A
ROM::Relation Ne
A
ROM::Mapping Ne
A
ROM::Session Ne
A
ROM::Mapper Ne
A
ROM::Schema Ne
A
ROM::Environment#session Ne
A
ROM::Relation#first Ne
A
ROM::Mapper.build Ne
A
ROM::Relation.build Ne
B
ROM::Mapper#identity_from_tuple Ne
B
ROM::Relation#replace Ne
B
ROM::Mapper#identity Ne
B
ROM::Relation#delete Ne
B
ROM::Relation#drop Ne
B
ROM::Mapper#call Ne
B
ROM::Schema#[] Ne
B
ROM::Environment#repository Ne
B
ROM::Session.start Ne
U
ROM::Session::ObjectNotTrackedError#initialize Ne
U
ROM::Session::Mapper#identity Ne
U
ROM::Relation#initialize Ne
U
ROM::Relation#mapper Ne
A
ROM::Relation#each E
A
Axiom::Adapter E
C
ROM::Session::Relation#dirty? E
Show 159 low priority objects ...

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

This page is for rom-rb/rom 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.