rom-rb/rom Rom

Data mapping and persistence toolkit for Ruby

Refresh
#390 (all)
Ruby (change)
13 seconds
almost 4 years ago

Here you can see the build history of your project.

In case the documentation changed, it is shown here.

#392 6 seconds almost 4 years ago
7 builds omitted (no changes to documentation).
#381 Update lint test [6ce49f53] 13 seconds almost 4 years ago
A
ROM::Adapter::Lint::TestRepository Ne
U
ROM::Adapter::Lint::TestRepository#test_dataset_predicate Ne
U
ROM::Adapter::Lint::TestRepository#test_dataset_reader Ne
U
ROM::Adapter::Lint::TestRepository#test_schemes Ne
U
ROM::Adapter::Lint::TestRepository#repository Ne
U
ROM::Adapter::Lint::TestRepository#test_setup Ne
U
ROM::Adapter::Lint::TestRepository#uri Ne
Show 1 low priority object ...
1 build omitted (no changes to documentation).
#378 Replace Adapter with Repository [bb4d78bd] 12 seconds almost 4 years ago
A
ROM::Env#read Ne
U
ROM::Env#repositories Ne
U
ROM::Env#relations Ne
U
ROM::Env#mappers Ne
U
ROM::Adapter::Memory::Commands::Create Ne
B
ROM::Commands::AbstractCommand#call Ne
A
ROM::Commands::WithOptions Ne
A
ROM::Reader Ne
U
ROM::Commands::Update#set Ne
U
ROM::Env#commands Ne
A
ROM::Commands::Create E
A
ROM::Commands::Update E
A
ROM::Commands::Delete E
A
ROM::Commands::Delete#target E
B
ROM::Commands::Update#call E
B
ROM::Commands::Delete#call E
U
ROM::Commands::Delete#initialize E
A
ROM::Relation Ne
U
ROM::Processor::Transproc#to_transproc Ne
U
ROM::Processor::Transproc#initialize Ne
U
ROM::Processor::Transproc#mapping Ne
U
ROM::Processor::Transproc#header Ne
U
ROM::Processor::Transproc#model Ne
U
ROM::Processor::Transproc Ne
A
ROM::Global Ne
U
ROM::Setup::MapperDSL#initialize Ne
U
ROM::Setup::MapperDSL#define Ne
A
ROM::Processor Ne
U
ROM::Setup::CommandDSL::CommandDefinition Ne
U
ROM::Setup::CommandDSL#commands Ne
U
ROM::Setup::MapperDSL#mappers Ne
U
ROM::Setup::CommandDSL Ne
U
ROM::Setup::MapperDSL Ne
A
ROM::Processor::Transproc.build E
A
ROM::Commands::Result#to_ary Ne
A
ROM::Commands::Result::Success Ne
A
ROM::Commands::Result::Failure Ne
A
ROM::Commands::Result Ne
A
ROM::CommandRegistry Ne
A
ROM::Commands::Result#error Ne
A
ROM::Commands::Result#value Ne
B
ROM::Commands::Result::Failure#> Ne
B
ROM::Commands::Result::Success#> Ne
U
ROM::CommandRegistry::Evaluator Ne
A
ROM::Commands::Result::Success#to_ary E
A
ROM::Commands::Result::Failure#to_ary E
U
ROM::Setup::CommandDSL#initialize Ne
U
ROM::Setup::CommandDSL#define Ne
A
ROM::Reader#each Ne
U
ROM::Setup::CommandDSL::CommandDefinition#to_h Ne
U
ROM::ClassBuilder#call Ne
U
ROM::Reader#to_ary Ne
U
ROM::ClassBuilder Ne
U
ROM::Setup::CommandDSL::CommandDefinition#initialize E
U
ROM::Setup::CommandDSL::CommandDefinition#method_missing E
B
ROM::CommandRegistry::Evaluator#evaluate Ne
B
ROM::CommandRegistry::Evaluator#method_missing E
A
ROM::CommandRegistry#try Ne
A
ROM::Commands::AbstractCommand#target Ne
U
ROM::Commands::AbstractCommand#relation Ne
U
ROM::Commands::AbstractCommand Ne
U
ROM::EnumerableDataset#to_ary Ne
A
ROM::ArrayDataset E
A
ROM::EnumerableDataset Ne
U
ROM::Processor::Transproc#row_proc Ne
U
ROM::Relation#dataset Ne
A
ROM::Reader#one! N
A
ROM::Reader#one E
A
ROM::Relation#to_a Ne
B
ROM::Setup#relation Ne
A
ROM::Env#command Ne
A
ROM::Setup Ne
A
ROM::Env Ne
B
ROM::Global#setup N
B
ROM::Setup#commands Ne
B
ROM::Setup#mappers Ne
A
ROM::Setup#finalize Ne
A
ROM::Repository#command N
U
ROM::Adapter::Memory::Dataset#insert N
U
ROM::Global#commands N
U
ROM::Global#mappers N
U
ROM N
C
ROM::Global#relation Ne
U
ROM::Adapter::Memory::Dataset#project Ne
U
ROM::Adapter::Memory::Dataset#order Ne
U
ROM::Adapter::Memory::Dataset#join Ne
A
ROM::Adapter::Lint::TestEnumerableDataset Ne
A
ROM::Adapter::Memory::Storage#initialize Ne
A
ROM::Repository#extend_relation_instance Ne
A
ROM::Repository#extend_relation_class Ne
A
ROM::Adapter::Lint::TestAdapter Ne
A
ROM::Repository#connection Ne
A
ROM::Repository#options Ne
A
ROM::Repository#uri Ne
A
ROM::Repository Ne
A
ROM::Repository#disconnect Ne
A
ROM::Repository.setup Ne
U
ROM::Adapter::Lint::TestAdapter#test_dataset_predicate Ne
U
ROM::Adapter::Lint::TestEnumerableDataset#test_each Ne
U
ROM::Adapter::Lint::TestAdapter#test_dataset_reader Ne
U
ROM::Adapter::Lint::TestEnumerableDataset#test_to_a Ne
U
ROM::Adapter::Lint::TestEnumerableDataset#dataset Ne
U
ROM::Adapter::Lint::TestEnumerableDataset#data Ne
U
ROM::Adapter::Memory::Storage#create_dataset Ne
U
ROM::Adapter::Lint::TestAdapter#test_schemes Ne
U
ROM::Adapter::Lint::TestAdapter#test_setup Ne
U
ROM::Adapter::Memory::Repository.schemes Ne
U
ROM::Adapter::Memory::Repository#dataset Ne
U
ROM::Adapter::Lint::TestAdapter#adapter Ne
U
ROM::Adapter::Memory::Commands::Update Ne
U
ROM::Adapter::Memory::Commands::Delete Ne
U
ROM::Adapter::Memory::Dataset#restrict Ne
U
ROM::Adapter::Memory::Dataset#delete Ne
U
ROM::Adapter::Lint::TestAdapter#uri Ne
U
ROM::Adapter::Memory::Repository#[] Ne
U
ROM::Adapter::Memory::Storage#data Ne
U
ROM::Adapter::Memory::Storage#size Ne
U
ROM::Adapter::Memory::Repository Ne
U
ROM::Adapter::Memory::Storage#[] Ne
U
ROM::Adapter::Memory::Dataset Ne
U
ROM::Adapter::Memory::Storage Ne
U
ROM::Repository#use_logger Ne
U
ROM::Repository#logger Ne
U
ROM::Global#finalize Ne
U
ROM::Global#env Ne
A
ROM::Repository.[] E
A
ROM::Adapter::Memory::Repository#command_namespace E
A
ROM::Adapter::Memory::Commands::Update#execute E
A
ROM::Adapter::Memory::Commands::Create#execute E
A
ROM::Adapter::Memory::Commands::Delete#execute E
A
ROM::Adapter::Memory::Repository#setup E
U
ROM::Adapter::Memory::Repository#use_logger E
U
ROM::Adapter::Memory::Repository#logger E
Show 243 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.