Let's raise the visibility of code documentation in Ruby! What is this about?

solnic/virtus

Attributes on Steroids for Plain Old Ruby Objects – Read the documentation

This page shows an evaluation of the documentation of solnic/virtus.

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
Virtus
A
Virtus::InstanceMethods#set_default_attributes!
A
Virtus::InstanceMethods::MassAssignment#attributes
A
Virtus::ValueObject::InstanceMethods#clone
A
Virtus::Attribute
Show 62 more ...
A
Virtus::InstanceMethods::MassAssignment#attributes=
A
Virtus::Attribute::Accessor#set_default_value
A
Virtus::ValueObject::ClassMethods#equalizer
A
Virtus::Extensions::AllowedWriterMethods
A
Virtus::InstanceMethods::MassAssignment
A
Virtus::Attribute::Collection::Type
A
Virtus::TypeLookup#determine_type
A
Virtus::Attribute::EmbeddedValue
A
Virtus::Attribute::Accessor#name
A
Virtus::Options#accepted_options
A
Virtus::Attribute::Accessor#set
A
Virtus::Attribute::Accessor#get
A
Virtus::InstanceMethods#freeze
A
Virtus::Attribute::Collection
A
Virtus::Model::MassAssignment
A
Virtus::Equalizer::Methods#==
A
Virtus::Attribute::Coercible
A
Virtus::InstanceMethods#[]=
A
Virtus::Attribute::Accessor
A
Virtus::InstanceMethods#[]
A
Virtus::Model::Constructor
A
Virtus::AttributeSet#merge
A
Virtus::Equalizer::Methods
A
Virtus::Attribute::Boolean
A
Virtus::Attribute::Strict
A
Virtus::Attribute#rename
A
Virtus::AttributeSet#[]=
A
Virtus::Attribute#coerce
A
Virtus::AttributeSet#<<
A
Virtus::AttributeSet#[]
A
Virtus::Options#options
A
Virtus::InstanceMethods
A
Virtus::Attribute::Hash
A
Virtus::ClassInclusions
A
Virtus::Attribute.build
A
Virtus::Attribute#type
A
Virtus::Configuration
A
Virtus::ClassMethods
A
Virtus::Coercer#call
A
Virtus::AttributeSet
A
Virtus::ValueObject
A
Virtus::TypeLookup
A
Virtus::Extensions
A
Virtus::Equalizer
A
Virtus.finalize
A
Virtus::Coercer
A
Virtus::Options
A
Virtus::Configuration#mass_assignment=
A
Virtus::Configuration#mass_assignment
A
Virtus::Configuration#constructor=
A
Virtus::Configuration#constructor
A
Virtus::Configuration#finalize=
A
Virtus::Configuration#finalize
A
Virtus::Configuration#coerce=
A
Virtus::Configuration#strict=
A
Virtus::Configuration#coerce
A
Virtus::Configuration#strict
A
Virtus::ValueObject::ClassMethods#attribute
A
Virtus::Extensions::Methods#attribute
A
Virtus::AttributeSet#each
A
Virtus::Attribute::Collection#coerce
A
Virtus::ClassMethods#attribute_set
Proper documentation present
B
Virtus::Options#accept_options
B
Virtus.value_object
B
Virtus::ValueObject::InstanceMethods#with
B
Virtus::InstanceMethods#reset_attribute
B
Virtus::Attribute::Coercible#set
Needs work
C
Virtus::Extensions::Methods#values
C
Virtus::ClassMethods#attributes
C
Virtus::Attribute.coerce
C
Virtus::Attribute::Strict#coerce
Undocumented
U
Virtus.coercer
U
Virtus.module
U
Virtus.config
U
Virtus.model
U
Virtus::Attribute::Collection::Type#member_type=
Show 24 more ...
U
Virtus::Attribute::Collection::Type#member_type
U
Virtus::Attribute::Collection::Type#primitive=
U
Virtus::Attribute::Collection::Type#primitive
U
Virtus::ValueObject::AllowedWriterMethods
U
Virtus::ValueObject::InstanceMethods
U
Virtus::InstanceMethods::Constructor
U
Virtus::CoercionError#attribute_name
U
Virtus::CoercionError#build_message
U
Virtus::Attribute::LazyDefault#get
U
Virtus::ValueObject::ClassMethods
U
Virtus::CoercionError#target_type
U
Virtus::CoercionError#initialize
U
Virtus::ClassInclusions::Methods
U
Virtus::CoercionError#attribute
U
Virtus::Attribute::LazyDefault
U
Virtus::ConstMissingExtensions
U
Virtus::CoercionError#output
U
Virtus::Extensions::Methods
U
Virtus::CoercionError
U
Virtus::Model::Core
U
Virtus.coerce=
U
Virtus::Model
U
Virtus.coerce
U
Virtus::Attribute.merge_options!

Let's raise the visibility of documentation in Ruby!

This page is for solnic/virtus 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?

Sure!

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.

Fork me on GitHub