rom-rb/rom
Ruby Object Mapper – Read the documentation
This page shows an evaluation of the documentation of rom-rb/rom.
Each class, module, method, etc. is given a grade based on how complete the docs are.
The bar above shows the distribution of these grades.
| Seems really good | ||
|---|---|---|
|
A
|
ROM::Mapper |
|
|
A
|
ROM::Relation |
|
|
A
|
ROM::Environment.setup |
|
|
A
|
ROM::Session::ObjectNotTrackedError |
|
|
A
|
ROM::Session::Environment#[] |
|
| Show 23 more ... | ||
|
A
|
ROM::Relation::MapperBuilder |
|
|
A
|
Axiom::Adapter::DataObjects |
|
|
A
|
Axiom::Adapter#uri_scheme |
|
|
A
|
ROM::Environment::Builder |
|
|
A
|
ROM::Session::Environment |
|
|
A
|
ROM::Environment#mappers |
|
|
A
|
ROM::Environment#schema |
|
|
A
|
ROM::Session::Relation |
|
|
A
|
ROM::Schema::Builder |
|
|
A
|
ROM::Repository#[]= |
|
|
A
|
ROM::Repository#[] |
|
|
A
|
ROM::Relation#last |
|
|
A
|
ROM::Relation#take |
|
|
A
|
ROM::Session#flush |
|
|
A
|
ROM::Relation#one |
|
|
A
|
ROM::Environment |
|
|
A
|
ROM::Schema#[] |
|
|
A
|
ROM::Session |
|
|
A
|
ROM::Schema |
|
|
A
|
ROM::Environment#session |
|
|
A
|
ROM::Relation#each |
|
|
A
|
ROM::Relation#first |
|
|
A
|
Axiom::Adapter |
|
| Proper documentation present | ||
|---|---|---|
|
B
|
ROM::Relation#insert |
|
|
B
|
ROM::Mapper.build |
|
|
B
|
ROM::Session::Relation#new |
|
|
B
|
ROM::Mapper#new_object |
|
|
B
|
ROM::Environment#[] |
|
| Show 17 more ... | ||
|
B
|
ROM::Mapper#identity_from_tuple |
|
|
B
|
ROM::Schema::Builder#[] |
|
|
B
|
ROM::Relation#project |
|
|
B
|
ROM::Relation#replace |
|
|
B
|
ROM::Relation#delete |
|
|
B
|
ROM::Relation#rename |
|
|
B
|
ROM::Mapper#identity |
|
|
B
|
ROM::Relation#group |
|
|
B
|
ROM::Relation#wrap |
|
|
B
|
ROM::Relation#drop |
|
|
B
|
ROM::Relation#join |
|
|
B
|
ROM::Environment#repository |
|
|
B
|
ROM::Session.start |
|
|
B
|
ROM::Mapper#group |
|
|
B
|
ROM::Mapper#load |
|
|
B
|
ROM::Mapper#dump |
|
|
B
|
ROM::Mapper#wrap |
|
| Needs work | ||
|---|---|---|
|
C
|
ROM::Session::Relation#identity |
|
|
C
|
ROM::Session::Relation#delete |
|
|
C
|
ROM::Session::Relation#track |
|
|
C
|
ROM::Session::Relation#state |
|
|
C
|
ROM::Session::Relation#save |
|
| Show 7 more ... | ||
|
C
|
ROM::Session::Relation#delete! |
|
|
C
|
ROM::Session::Relation#update! |
|
|
C
|
ROM::Session::Relation#insert! |
|
|
C
|
ROM::Session::Relation#update_attributes |
|
|
C
|
ROM::Relation#update |
|
|
C
|
ROM::Session#[] |
|
|
C
|
ROM::Session::Relation#dirty? |
|
| Undocumented | ||
|---|---|---|
|
U
|
ROM::Relation::MapperBuilder.call |
|
|
U
|
ROM::Relation#restrict |
|
|
U
|
ROM::Relation#sort_by |
|
|
U
|
ROM::Relation::MapperBuilder#relation |
|
|
U
|
ROM::Relation::MapperBuilder#call |
|
| Show 24 more ... | ||
|
U
|
Axiom |
|
|
U
|
ROM |
|
|
U
|
ROM::Session::ObjectNotTrackedError#initialize |
|
|
U
|
ROM::Relation::MapperBuilder#definitions |
|
|
U
|
ROM::Relation::MapperBuilder#mappers |
|
|
U
|
ROM::Relation::MapperBuilder#automap |
|
|
U
|
ROM::Environment::Builder#relations |
|
|
U
|
ROM::Session::Relation#identity_map |
|
|
U
|
ROM::Schema::Builder#automapped |
|
|
U
|
ROM::Schema::Builder#relations |
|
|
U
|
ROM::Session::Relation#tracker |
|
|
U
|
ROM::Schema::Builder#options |
|
|
U
|
ROM::Relation#reader |
|
|
U
|
ROM::Relation#mapper |
|
|
U
|
ROM::Mapper#project |
|
|
U
|
ROM::Mapper#options |
|
|
U
|
ROM::Mapper#rename |
|
|
U
|
ROM::Mapper#dumper |
|
|
U
|
ROM::Mapper#header |
|
|
U
|
ROM::Mapper#loader |
|
|
U
|
ROM::Mapper#model |
|
|
U
|
ROM::Relation.new |
|
|
U
|
ROM::Mapper#join |
|
|
U
|
ROM::Mapper#type |
|
Let's raise the visibility of documentation in Ruby!
This page is for rom-rb/rom and is part of a project called "Inch Pages", showing documentation measurements provided by Inch.
Inch Pages also provides a badge: 
(not counting low priority objects)
Can I have my own badges?
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.
nch Pages