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

hajee/easy_type

Build a complex puppet custom type and provider, the easy way – Read the documentation

This page shows an evaluation of the documentation of hajee/easy_type.

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
EasyType
A
EasyType::Type::ClassMethods#parameter
A
EasyType::Type::ClassMethods#to_get_raw_resources
A
EasyType::Type::ClassMethods#on_destroy
A
EasyType::Type::ClassMethods#on_modify
Show 33 more ...
A
EasyType::Type::ClassMethods#on_create
A
EasyType::Type::ClassMethods#group
A
EasyType::Helpers::InstancesResults
A
EasyType::Type::ClassMethods#groups
A
EasyType::Provider::ClassMethods
A
EasyType::Mungers::Upcase
A
EasyType::Mungers::Size
A
EasyType::Type#commands
A
EasyType::ScriptBuilder
A
BlankSlate#initialize
A
EasyType::Type#groups
A
EasyType::Parameter
A
EasyType::Template
A
EasyType::Provider
A
EasyType::Helpers
A
EasyType::Group
A
EasyType::Type
A
EasyType::Provider::ClassMethods#mk_resource_methods
A
EasyType::Provider::ClassMethods#prefetch
A
EasyType::ScriptBuilder#line=
A
EasyType::ScriptBuilder#line
A
EasyType::Provider#destroy
A
EasyType::Provider#create
A
EasyType::Provider#flush
A
EasyType::Helpers::InstancesResults#column_data
A
EasyType::Provider::ClassMethods#instances
A
EasyType::FileIncluder#include_file
A
EasyType::Validators::Integer
A
EasyType::Group#contents_for
A
EasyType::Template#template
A
EasyType::Validators::Name
A
EasyType::Group#group_for
A
EasyType::Group#add
Proper documentation present
B
EasyType::Helpers#convert_csv_data_to_hash
B
CommandEntry.set_binding
B
CommandEntry#initialize
Needs work
C
EasyType::Type::ClassMethods#set_command
Undocumented
U
#file_is_included
U
CommandEntry
U
BlankSlate
U
#ruby_19
U
#ruby_18
Show 34 more ...
U
EasyType::Type#method_missing
U
EasyType::ScriptBuilder#add
U
EasyType::ScriptBuilder#initialize
U
EasyType::ScriptBuilder#before
U
EasyType::ScriptBuilder#append
U
EasyType::ScriptBuilder#after
U
EasyType::Type::ClassMethods#process_group_entry
U
EasyType::ScriptBuilder#acceptable_commands
U
EasyType::Mungers::Downcase#unsafe_munge
U
EasyType::ScriptBuilder#default_command
U
EasyType::ScriptBuilder#last_command
U
EasyType::Provider#property_flush
U
EasyType::Provider#property_hash
U
EasyType::ScriptBuilder#entries
U
EasyType::ScriptBuilder#execute
U
EasyType::ScriptBuilder#results
U
EasyType::ScriptBuilder#binding
U
EasyType::Type::ClassMethods
U
EasyType::Mungers::Downcase
U
EasyType::Mungers::Integer
U
EasyType::ScriptBuilder#<<
U
CommandEntry#arguments
U
EasyType::FileIncluder
U
BlankSlate#eigenclass
U
CommandEntry#command
U
CommandEntry#execute
U
CommandEntry#context
U
BlankSlate#entries=
U
BlankSlate#results=
U
BlankSlate#results
U
BlankSlate#entries
U
BlankSlate#execute
U
BlankSlate#type=
U
BlankSlate#type

Let's raise the visibility of documentation in Ruby!

This page is for hajee/easy_type 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