yard 0.9.18 → 0.9.23
Sign up to get free protection for your applications and to get access to all the features.
Potentially problematic release.
This version of yard might be problematic. Click here for more details.
- checksums.yaml +4 -4
- data/.dockerignore +2 -0
- data/.github/ISSUE_TEMPLATE.md +33 -0
- data/.github/PULL_REQUEST_TEMPLATE.md +12 -0
- data/.gitignore +14 -0
- data/.rspec +2 -0
- data/.rubocop.yml +99 -0
- data/.travis.yml +52 -0
- data/.yardopts +26 -26
- data/.yardopts_guide +19 -0
- data/.yardopts_i18n +23 -0
- data/CHANGELOG.md +781 -728
- data/CODE_OF_CONDUCT.md +15 -0
- data/CONTRIBUTING.md +140 -0
- data/Dockerfile.samus +28 -0
- data/Gemfile +32 -0
- data/LEGAL +66 -66
- data/LICENSE +22 -22
- data/README.md +330 -328
- data/Rakefile +37 -53
- data/SECURITY.md +26 -0
- data/benchmarks/builtins_vs_eval.rb +24 -24
- data/benchmarks/concat_vs_join.rb +13 -13
- data/benchmarks/erb_vs_erubis.rb +54 -54
- data/benchmarks/format_args.rb +47 -47
- data/benchmarks/generation.rb +38 -38
- data/benchmarks/marshal_vs_dbm.rb +64 -64
- data/benchmarks/parsing.rb +46 -46
- data/benchmarks/pathname_vs_string.rb +50 -50
- data/benchmarks/rdoc_vs_yardoc.rb +11 -11
- data/benchmarks/registry_store_types.rb +49 -49
- data/benchmarks/ri_vs_yri.rb +19 -19
- data/benchmarks/ripper_parser.rb +13 -13
- data/benchmarks/splat_vs_flatten.rb +13 -13
- data/benchmarks/template_erb.rb +23 -23
- data/benchmarks/template_format.rb +7 -7
- data/benchmarks/template_profile.rb +18 -18
- data/benchmarks/yri_cache.rb +20 -20
- data/bin/yard +13 -13
- data/bin/yardoc +13 -13
- data/bin/yri +13 -13
- data/docs/CodeObjects.md +115 -115
- data/docs/GettingStarted.md +679 -679
- data/docs/Handlers.md +152 -152
- data/docs/Overview.md +61 -61
- data/docs/Parser.md +191 -191
- data/docs/Tags.md +283 -283
- data/docs/TagsArch.md +123 -123
- data/docs/Templates.md +496 -496
- data/docs/WhatsNew.md +1245 -1245
- data/docs/templates/default/fulldoc/html/full_list_tag.erb +8 -8
- data/docs/templates/default/fulldoc/html/setup.rb +6 -6
- data/docs/templates/default/layout/html/setup.rb +9 -9
- data/docs/templates/default/layout/html/tag_list.erb +11 -11
- data/docs/templates/default/yard_tags/html/list.erb +18 -18
- data/docs/templates/default/yard_tags/html/setup.rb +26 -26
- data/docs/templates/plugin.rb +70 -70
- data/lib/rubygems_plugin.rb +9 -9
- data/lib/yard.rb +69 -69
- data/lib/yard/autoload.rb +308 -303
- data/lib/yard/cli/command.rb +85 -85
- data/lib/yard/cli/command_parser.rb +93 -93
- data/lib/yard/cli/config.rb +198 -198
- data/lib/yard/cli/diff.rb +270 -270
- data/lib/yard/cli/display.rb +69 -69
- data/lib/yard/cli/gems.rb +84 -84
- data/lib/yard/cli/graph.rb +125 -125
- data/lib/yard/cli/help.rb +20 -20
- data/lib/yard/cli/i18n.rb +70 -70
- data/lib/yard/cli/list.rb +23 -23
- data/lib/yard/cli/markup_types.rb +32 -32
- data/lib/yard/cli/server.rb +257 -257
- data/lib/yard/cli/stats.rb +231 -231
- data/lib/yard/cli/yardoc.rb +789 -788
- data/lib/yard/cli/yardopts_command.rb +110 -110
- data/lib/yard/cli/yri.rb +215 -215
- data/lib/yard/code_objects/base.rb +622 -615
- data/lib/yard/code_objects/class_object.rb +146 -146
- data/lib/yard/code_objects/class_variable_object.rb +11 -11
- data/lib/yard/code_objects/constant_object.rb +16 -16
- data/lib/yard/code_objects/extended_method_object.rb +24 -24
- data/lib/yard/code_objects/extra_file_object.rb +134 -131
- data/lib/yard/code_objects/macro_object.rb +172 -172
- data/lib/yard/code_objects/method_object.rb +196 -196
- data/lib/yard/code_objects/module_object.rb +21 -21
- data/lib/yard/code_objects/namespace_mapper.rb +114 -114
- data/lib/yard/code_objects/namespace_object.rb +200 -200
- data/lib/yard/code_objects/proxy.rb +244 -240
- data/lib/yard/code_objects/root_object.rb +19 -19
- data/lib/yard/config.rb +270 -270
- data/lib/yard/core_ext/array.rb +16 -16
- data/lib/yard/core_ext/file.rb +69 -69
- data/lib/yard/core_ext/hash.rb +16 -16
- data/lib/yard/core_ext/insertion.rb +63 -63
- data/lib/yard/core_ext/module.rb +11 -20
- data/lib/yard/core_ext/string.rb +68 -68
- data/lib/yard/core_ext/symbol_hash.rb +75 -75
- data/lib/yard/docstring.rb +386 -386
- data/lib/yard/docstring_parser.rb +345 -345
- data/lib/yard/gem_index.rb +29 -29
- data/lib/yard/globals.rb +22 -22
- data/lib/yard/handlers/base.rb +595 -595
- data/lib/yard/handlers/c/alias_handler.rb +16 -16
- data/lib/yard/handlers/c/attribute_handler.rb +13 -13
- data/lib/yard/handlers/c/base.rb +129 -129
- data/lib/yard/handlers/c/class_handler.rb +27 -27
- data/lib/yard/handlers/c/constant_handler.rb +13 -13
- data/lib/yard/handlers/c/handler_methods.rb +212 -211
- data/lib/yard/handlers/c/init_handler.rb +20 -20
- data/lib/yard/handlers/c/method_handler.rb +45 -45
- data/lib/yard/handlers/c/mixin_handler.rb +21 -21
- data/lib/yard/handlers/c/module_handler.rb +17 -17
- data/lib/yard/handlers/c/override_comment_handler.rb +31 -31
- data/lib/yard/handlers/c/path_handler.rb +11 -11
- data/lib/yard/handlers/c/struct_handler.rb +13 -13
- data/lib/yard/handlers/c/symbol_handler.rb +8 -8
- data/lib/yard/handlers/common/method_handler.rb +19 -0
- data/lib/yard/handlers/processor.rb +200 -200
- data/lib/yard/handlers/ruby/alias_handler.rb +45 -44
- data/lib/yard/handlers/ruby/attribute_handler.rb +87 -87
- data/lib/yard/handlers/ruby/base.rb +165 -165
- data/lib/yard/handlers/ruby/class_condition_handler.rb +92 -92
- data/lib/yard/handlers/ruby/class_handler.rb +119 -119
- data/lib/yard/handlers/ruby/class_variable_handler.rb +17 -17
- data/lib/yard/handlers/ruby/comment_handler.rb +10 -10
- data/lib/yard/handlers/ruby/constant_handler.rb +55 -59
- data/lib/yard/handlers/ruby/decorator_handler_methods.rb +123 -123
- data/lib/yard/handlers/ruby/dsl_handler.rb +15 -15
- data/lib/yard/handlers/ruby/dsl_handler_methods.rb +96 -96
- data/lib/yard/handlers/ruby/exception_handler.rb +27 -27
- data/lib/yard/handlers/ruby/extend_handler.rb +22 -22
- data/lib/yard/handlers/ruby/legacy/alias_handler.rb +37 -37
- data/lib/yard/handlers/ruby/legacy/attribute_handler.rb +65 -65
- data/lib/yard/handlers/ruby/legacy/base.rb +245 -245
- data/lib/yard/handlers/ruby/legacy/class_condition_handler.rb +83 -83
- data/lib/yard/handlers/ruby/legacy/class_handler.rb +113 -113
- data/lib/yard/handlers/ruby/legacy/class_variable_handler.rb +15 -15
- data/lib/yard/handlers/ruby/legacy/comment_handler.rb +10 -10
- data/lib/yard/handlers/ruby/legacy/constant_handler.rb +29 -29
- data/lib/yard/handlers/ruby/legacy/dsl_handler.rb +17 -17
- data/lib/yard/handlers/ruby/legacy/exception_handler.rb +13 -13
- data/lib/yard/handlers/ruby/legacy/extend_handler.rb +21 -21
- data/lib/yard/handlers/ruby/legacy/method_handler.rb +90 -90
- data/lib/yard/handlers/ruby/legacy/mixin_handler.rb +39 -39
- data/lib/yard/handlers/ruby/legacy/module_function_handler.rb +19 -19
- data/lib/yard/handlers/ruby/legacy/module_handler.rb +12 -12
- data/lib/yard/handlers/ruby/legacy/private_class_method_handler.rb +22 -22
- data/lib/yard/handlers/ruby/legacy/private_constant_handler.rb +22 -22
- data/lib/yard/handlers/ruby/legacy/visibility_handler.rb +17 -17
- data/lib/yard/handlers/ruby/legacy/yield_handler.rb +29 -29
- data/lib/yard/handlers/ruby/method_condition_handler.rb +9 -9
- data/lib/yard/handlers/ruby/method_handler.rb +104 -118
- data/lib/yard/handlers/ruby/mixin_handler.rb +49 -37
- data/lib/yard/handlers/ruby/module_function_handler.rb +27 -27
- data/lib/yard/handlers/ruby/module_handler.rb +12 -12
- data/lib/yard/handlers/ruby/private_class_method_handler.rb +14 -14
- data/lib/yard/handlers/ruby/private_constant_handler.rb +43 -43
- data/lib/yard/handlers/ruby/public_class_method_handler.rb +14 -14
- data/lib/yard/handlers/ruby/struct_handler_methods.rb +143 -143
- data/lib/yard/handlers/ruby/visibility_handler.rb +22 -22
- data/lib/yard/handlers/ruby/yield_handler.rb +31 -31
- data/lib/yard/i18n/locale.rb +67 -67
- data/lib/yard/i18n/message.rb +57 -57
- data/lib/yard/i18n/messages.rb +56 -56
- data/lib/yard/i18n/po_parser.rb +61 -61
- data/lib/yard/i18n/pot_generator.rb +290 -290
- data/lib/yard/i18n/text.rb +173 -173
- data/lib/yard/logging.rb +205 -205
- data/lib/yard/options.rb +217 -217
- data/lib/yard/parser/base.rb +57 -57
- data/lib/yard/parser/c/c_parser.rb +235 -235
- data/lib/yard/parser/c/comment_parser.rb +134 -134
- data/lib/yard/parser/c/statement.rb +66 -64
- data/lib/yard/parser/ruby/ast_node.rb +551 -540
- data/lib/yard/parser/ruby/legacy/irb/slex.rb +276 -0
- data/lib/yard/parser/ruby/legacy/ruby_lex.rb +1345 -1354
- data/lib/yard/parser/ruby/legacy/ruby_parser.rb +32 -32
- data/lib/yard/parser/ruby/legacy/statement.rb +68 -66
- data/lib/yard/parser/ruby/legacy/statement_list.rb +394 -394
- data/lib/yard/parser/ruby/legacy/token_list.rb +74 -74
- data/lib/yard/parser/ruby/ruby_parser.rb +699 -687
- data/lib/yard/parser/ruby/token_resolver.rb +156 -156
- data/lib/yard/parser/source_parser.rb +526 -526
- data/lib/yard/rake/yardoc_task.rb +81 -81
- data/lib/yard/registry.rb +439 -439
- data/lib/yard/registry_resolver.rb +231 -189
- data/lib/yard/registry_store.rb +342 -337
- data/lib/yard/rubygems/backports.rb +10 -10
- data/lib/yard/rubygems/backports/LICENSE.txt +57 -57
- data/lib/yard/rubygems/backports/MIT.txt +20 -20
- data/lib/yard/rubygems/backports/gem.rb +10 -10
- data/lib/yard/rubygems/backports/source_index.rb +365 -365
- data/lib/yard/rubygems/doc_manager.rb +90 -90
- data/lib/yard/rubygems/hook.rb +197 -197
- data/lib/yard/rubygems/specification.rb +50 -50
- data/lib/yard/serializers/base.rb +83 -83
- data/lib/yard/serializers/file_system_serializer.rb +123 -123
- data/lib/yard/serializers/process_serializer.rb +24 -24
- data/lib/yard/serializers/stdout_serializer.rb +34 -34
- data/lib/yard/serializers/yardoc_serializer.rb +152 -152
- data/lib/yard/server.rb +13 -13
- data/lib/yard/server/adapter.rb +100 -100
- data/lib/yard/server/commands/base.rb +209 -209
- data/lib/yard/server/commands/display_file_command.rb +29 -29
- data/lib/yard/server/commands/display_object_command.rb +65 -65
- data/lib/yard/server/commands/frames_command.rb +16 -16
- data/lib/yard/server/commands/library_command.rb +187 -187
- data/lib/yard/server/commands/library_index_command.rb +28 -28
- data/lib/yard/server/commands/list_command.rb +25 -25
- data/lib/yard/server/commands/root_request_command.rb +15 -15
- data/lib/yard/server/commands/search_command.rb +79 -79
- data/lib/yard/server/commands/static_file_command.rb +23 -23
- data/lib/yard/server/commands/static_file_helpers.rb +61 -62
- data/lib/yard/server/doc_server_helper.rb +91 -91
- data/lib/yard/server/doc_server_serializer.rb +39 -39
- data/lib/yard/server/library_version.rb +277 -277
- data/lib/yard/server/rack_adapter.rb +89 -89
- data/lib/yard/server/router.rb +187 -187
- data/lib/yard/server/static_caching.rb +46 -46
- data/lib/yard/server/templates/default/fulldoc/html/css/custom.css +127 -127
- data/lib/yard/server/templates/default/fulldoc/html/js/autocomplete.js +11 -11
- data/lib/yard/server/templates/default/layout/html/breadcrumb.erb +37 -37
- data/lib/yard/server/templates/default/layout/html/script_setup.erb +7 -7
- data/lib/yard/server/templates/default/layout/html/setup.rb +8 -8
- data/lib/yard/server/templates/default/method_details/html/permalink.erb +4 -4
- data/lib/yard/server/templates/default/method_details/html/setup.rb +5 -5
- data/lib/yard/server/templates/doc_server/library_list/html/headers.erb +8 -8
- data/lib/yard/server/templates/doc_server/library_list/html/library_list.erb +14 -14
- data/lib/yard/server/templates/doc_server/library_list/html/listing.erb +13 -13
- data/lib/yard/server/templates/doc_server/library_list/html/setup.rb +6 -6
- data/lib/yard/server/templates/doc_server/library_list/html/title.erb +2 -2
- data/lib/yard/server/templates/doc_server/processing/html/processing.erb +52 -52
- data/lib/yard/server/templates/doc_server/processing/html/setup.rb +4 -4
- data/lib/yard/server/templates/doc_server/search/html/search.erb +18 -18
- data/lib/yard/server/templates/doc_server/search/html/setup.rb +9 -9
- data/lib/yard/server/webrick_adapter.rb +45 -45
- data/lib/yard/tags/default_factory.rb +191 -191
- data/lib/yard/tags/default_tag.rb +13 -13
- data/lib/yard/tags/directives.rb +616 -616
- data/lib/yard/tags/library.rb +633 -633
- data/lib/yard/tags/option_tag.rb +13 -13
- data/lib/yard/tags/overload_tag.rb +71 -71
- data/lib/yard/tags/ref_tag.rb +8 -8
- data/lib/yard/tags/ref_tag_list.rb +28 -28
- data/lib/yard/tags/tag.rb +71 -71
- data/lib/yard/tags/tag_format_error.rb +7 -7
- data/lib/yard/tags/types_explainer.rb +162 -162
- data/lib/yard/templates/engine.rb +186 -186
- data/lib/yard/templates/erb_cache.rb +23 -23
- data/lib/yard/templates/helpers/base_helper.rb +215 -215
- data/lib/yard/templates/helpers/filter_helper.rb +27 -27
- data/lib/yard/templates/helpers/html_helper.rb +663 -646
- data/lib/yard/templates/helpers/html_syntax_highlight_helper.rb +78 -78
- data/lib/yard/templates/helpers/markup/rdoc_markdown.rb +23 -23
- data/lib/yard/templates/helpers/markup/rdoc_markup.rb +109 -109
- data/lib/yard/templates/helpers/markup_helper.rb +172 -172
- data/lib/yard/templates/helpers/method_helper.rb +75 -75
- data/lib/yard/templates/helpers/module_helper.rb +21 -21
- data/lib/yard/templates/helpers/text_helper.rb +112 -112
- data/lib/yard/templates/helpers/uml_helper.rb +47 -47
- data/lib/yard/templates/section.rb +105 -105
- data/lib/yard/templates/template.rb +418 -418
- data/lib/yard/templates/template_options.rb +92 -92
- data/lib/yard/verifier.rb +151 -151
- data/lib/yard/version.rb +6 -6
- data/po/ja.po +31108 -0
- data/samus.json +80 -0
- data/spec/cli/command_parser_spec.rb +43 -43
- data/spec/cli/command_spec.rb +36 -36
- data/spec/cli/config_spec.rb +148 -148
- data/spec/cli/diff_spec.rb +254 -254
- data/spec/cli/display_spec.rb +30 -30
- data/spec/cli/gems_spec.rb +81 -81
- data/spec/cli/graph_spec.rb +18 -18
- data/spec/cli/help_spec.rb +22 -22
- data/spec/cli/i18n_spec.rb +107 -107
- data/spec/cli/list_spec.rb +8 -8
- data/spec/cli/markup_types_spec.rb +22 -22
- data/spec/cli/server_spec.rb +324 -324
- data/spec/cli/stats_spec.rb +96 -96
- data/spec/cli/yard_on_yard_spec.rb +38 -38
- data/spec/cli/yardoc_spec.rb +896 -862
- data/spec/cli/yri_spec.rb +101 -101
- data/spec/code_objects/base_spec.rb +485 -470
- data/spec/code_objects/class_object_spec.rb +226 -226
- data/spec/code_objects/code_object_list_spec.rb +36 -36
- data/spec/code_objects/constants_spec.rb +116 -116
- data/spec/code_objects/extra_file_object_spec.rb +161 -160
- data/spec/code_objects/macro_object_spec.rb +150 -150
- data/spec/code_objects/method_object_spec.rb +184 -184
- data/spec/code_objects/module_object_spec.rb +142 -142
- data/spec/code_objects/namespace_object_spec.rb +171 -171
- data/spec/code_objects/proxy_spec.rb +147 -141
- data/spec/code_objects/spec_helper.rb +3 -3
- data/spec/config_spec.rb +171 -171
- data/spec/core_ext/array_spec.rb +13 -13
- data/spec/core_ext/file_spec.rb +72 -72
- data/spec/core_ext/hash_spec.rb +14 -14
- data/spec/core_ext/insertion_spec.rb +37 -37
- data/spec/core_ext/module_spec.rb +9 -15
- data/spec/core_ext/string_spec.rb +42 -42
- data/spec/core_ext/symbol_hash_spec.rb +89 -89
- data/spec/docstring_parser_spec.rb +280 -280
- data/spec/docstring_spec.rb +373 -373
- data/spec/handlers/alias_handler_spec.rb +82 -82
- data/spec/handlers/attribute_handler_spec.rb +96 -96
- data/spec/handlers/base_spec.rb +216 -216
- data/spec/handlers/c/alias_handler_spec.rb +34 -34
- data/spec/handlers/c/attribute_handler_spec.rb +41 -41
- data/spec/handlers/c/class_handler_spec.rb +78 -78
- data/spec/handlers/c/constant_handler_spec.rb +71 -71
- data/spec/handlers/c/init_handler_spec.rb +48 -48
- data/spec/handlers/c/method_handler_spec.rb +327 -325
- data/spec/handlers/c/mixin_handler_spec.rb +44 -44
- data/spec/handlers/c/module_handler_spec.rb +71 -71
- data/spec/handlers/c/override_comment_handler_spec.rb +47 -47
- data/spec/handlers/c/path_handler_spec.rb +36 -36
- data/spec/handlers/c/spec_helper.rb +23 -23
- data/spec/handlers/c/struct_handler_spec.rb +16 -16
- data/spec/handlers/class_condition_handler_spec.rb +87 -87
- data/spec/handlers/class_handler_spec.rb +247 -247
- data/spec/handlers/class_method_handler_shared_examples.rb +133 -133
- data/spec/handlers/class_variable_handler_spec.rb +12 -12
- data/spec/handlers/constant_handler_spec.rb +112 -112
- data/spec/handlers/decorator_handler_methods_spec.rb +393 -393
- data/spec/handlers/dsl_handler_spec.rb +226 -219
- data/spec/handlers/examples/alias_handler_001.rb.txt +45 -45
- data/spec/handlers/examples/attribute_handler_001.rb.txt +31 -31
- data/spec/handlers/examples/class_condition_handler_001.rb.txt +68 -68
- data/spec/handlers/examples/class_handler_001.rb.txt +120 -120
- data/spec/handlers/examples/class_variable_handler_001.rb.txt +9 -9
- data/spec/handlers/examples/constant_handler_001.rb.txt +35 -35
- data/spec/handlers/examples/dsl_handler_001.rb.txt +156 -154
- data/spec/handlers/examples/exception_handler_001.rb.txt +58 -58
- data/spec/handlers/examples/extend_handler_001.rb.txt +19 -16
- data/spec/handlers/examples/method_condition_handler_001.rb.txt +9 -9
- data/spec/handlers/examples/method_handler_001.rb.txt +128 -128
- data/spec/handlers/examples/mixin_handler_001.rb.txt +40 -37
- data/spec/handlers/examples/module_handler_001.rb.txt +29 -29
- data/spec/handlers/examples/private_constant_handler_001.rb.txt +8 -8
- data/spec/handlers/examples/process_handler_001.rb.txt +11 -11
- data/spec/handlers/examples/visibility_handler_001.rb.txt +35 -35
- data/spec/handlers/examples/yield_handler_001.rb.txt +54 -54
- data/spec/handlers/exception_handler_spec.rb +49 -49
- data/spec/handlers/extend_handler_spec.rb +28 -24
- data/spec/handlers/legacy_base_spec.rb +128 -128
- data/spec/handlers/method_condition_handler_spec.rb +15 -15
- data/spec/handlers/method_handler_spec.rb +214 -190
- data/spec/handlers/mixin_handler_spec.rb +60 -56
- data/spec/handlers/module_function_handler_spec.rb +106 -106
- data/spec/handlers/module_handler_spec.rb +35 -35
- data/spec/handlers/private_class_method_handler_spec.rb +11 -11
- data/spec/handlers/private_constant_handler_spec.rb +25 -25
- data/spec/handlers/processor_spec.rb +35 -35
- data/spec/handlers/public_class_method_handler_spec.rb +11 -11
- data/spec/handlers/ruby/base_spec.rb +95 -95
- data/spec/handlers/ruby/legacy/base_spec.rb +84 -84
- data/spec/handlers/spec_helper.rb +33 -33
- data/spec/handlers/visibility_handler_spec.rb +44 -44
- data/spec/handlers/yield_handler_spec.rb +52 -52
- data/spec/i18n/locale_spec.rb +81 -81
- data/spec/i18n/message_spec.rb +52 -52
- data/spec/i18n/messages_spec.rb +67 -67
- data/spec/i18n/pot_generator_spec.rb +295 -295
- data/spec/i18n/text_spec.rb +184 -184
- data/spec/logging_spec.rb +44 -44
- data/spec/options_spec.rb +171 -171
- data/spec/parser/base_spec.rb +24 -24
- data/spec/parser/c_parser_spec.rb +236 -236
- data/spec/parser/examples/array.c.txt +6267 -6267
- data/spec/parser/examples/example1.rb.txt +7 -7
- data/spec/parser/examples/extrafile.c.txt +8 -8
- data/spec/parser/examples/file.c.txt +28 -28
- data/spec/parser/examples/multifile.c.txt +22 -22
- data/spec/parser/examples/namespace.cpp.txt +68 -68
- data/spec/parser/examples/override.c.txt +424 -424
- data/spec/parser/examples/parse_in_order_001.rb.txt +2 -2
- data/spec/parser/examples/parse_in_order_002.rb.txt +1 -1
- data/spec/parser/examples/tag_handler_001.rb.txt +7 -7
- data/spec/parser/ruby/ast_node_spec.rb +33 -33
- data/spec/parser/ruby/legacy/statement_list_spec.rb +299 -299
- data/spec/parser/ruby/legacy/token_list_spec.rb +79 -79
- data/spec/parser/ruby/ruby_parser_spec.rb +508 -508
- data/spec/parser/ruby/token_resolver_spec.rb +165 -165
- data/spec/parser/source_parser_spec.rb +727 -727
- data/spec/parser/tag_parsing_spec.rb +17 -17
- data/spec/rake/yardoc_task_spec.rb +118 -118
- data/spec/registry_spec.rb +463 -463
- data/spec/registry_store_spec.rb +327 -316
- data/spec/rubygems/doc_manager_spec.rb +112 -112
- data/spec/serializers/data/serialized_yardoc/checksums +1 -1
- data/spec/serializers/file_system_serializer_spec.rb +145 -145
- data/spec/serializers/spec_helper.rb +2 -2
- data/spec/serializers/yardoc_serializer_spec.rb +78 -78
- data/spec/server/adapter_spec.rb +39 -39
- data/spec/server/commands/base_spec.rb +91 -91
- data/spec/server/commands/library_command_spec.rb +39 -39
- data/spec/server/doc_server_helper_spec.rb +72 -72
- data/spec/server/doc_server_serializer_spec.rb +60 -60
- data/spec/server/rack_adapter_spec.rb +21 -21
- data/spec/server/router_spec.rb +123 -123
- data/spec/server/spec_helper.rb +22 -22
- data/spec/server/static_caching_spec.rb +47 -47
- data/spec/server/webrick_servlet_spec.rb +20 -20
- data/spec/server_spec.rb +19 -19
- data/spec/spec_helper.rb +212 -212
- data/spec/tags/default_factory_spec.rb +168 -168
- data/spec/tags/default_tag_spec.rb +11 -11
- data/spec/tags/directives_spec.rb +463 -463
- data/spec/tags/library_spec.rb +48 -48
- data/spec/tags/overload_tag_spec.rb +53 -53
- data/spec/tags/ref_tag_list_spec.rb +53 -53
- data/spec/tags/types_explainer_spec.rb +203 -203
- data/spec/templates/class_spec.rb +45 -45
- data/spec/templates/constant_spec.rb +41 -41
- data/spec/templates/engine_spec.rb +131 -131
- data/spec/templates/examples/class001.html +308 -308
- data/spec/templates/examples/class001.txt +36 -36
- data/spec/templates/examples/class002.html +39 -39
- data/spec/templates/examples/constant001.txt +24 -24
- data/spec/templates/examples/constant002.txt +6 -6
- data/spec/templates/examples/constant003.txt +10 -10
- data/spec/templates/examples/method001.html +137 -137
- data/spec/templates/examples/method001.txt +35 -35
- data/spec/templates/examples/method002.html +91 -91
- data/spec/templates/examples/method002.txt +20 -20
- data/spec/templates/examples/method003.html +165 -165
- data/spec/templates/examples/method003.txt +45 -45
- data/spec/templates/examples/method004.html +48 -48
- data/spec/templates/examples/method004.txt +10 -10
- data/spec/templates/examples/method005.html +105 -105
- data/spec/templates/examples/method005.txt +33 -33
- data/spec/templates/examples/method006.html +107 -107
- data/spec/templates/examples/method006.txt +20 -20
- data/spec/templates/examples/module001.dot +33 -33
- data/spec/templates/examples/module001.html +833 -833
- data/spec/templates/examples/module001.txt +33 -33
- data/spec/templates/examples/module002.html +341 -341
- data/spec/templates/examples/module003.html +202 -202
- data/spec/templates/examples/module004.html +394 -394
- data/spec/templates/examples/module005.html +81 -81
- data/spec/templates/examples/tag001.txt +82 -82
- data/spec/templates/helpers/base_helper_spec.rb +171 -171
- data/spec/templates/helpers/html_helper_spec.rb +687 -668
- data/spec/templates/helpers/html_syntax_highlight_helper_spec.rb +65 -65
- data/spec/templates/helpers/markup/rdoc_markup_spec.rb +84 -84
- data/spec/templates/helpers/markup_helper_spec.rb +136 -136
- data/spec/templates/helpers/method_helper_spec.rb +107 -107
- data/spec/templates/helpers/module_helper_spec.rb +35 -35
- data/spec/templates/helpers/shared_signature_examples.rb +126 -126
- data/spec/templates/helpers/text_helper_spec.rb +65 -65
- data/spec/templates/markup_processor_integrations/asciidoctor_spec.rb +60 -0
- data/spec/templates/markup_processor_integrations/integration_spec_helper.rb +46 -0
- data/spec/templates/markup_processor_integrations/rdoc_markdown_spec.rb +59 -0
- data/spec/templates/markup_processor_integrations/rdoc_spec.rb +39 -0
- data/spec/templates/markup_processor_integrations/redcarpet_spec.rb +59 -0
- data/spec/templates/markup_processor_integrations/redcloth_spec.rb +48 -0
- data/spec/templates/method_spec.rb +118 -118
- data/spec/templates/module_spec.rb +203 -203
- data/spec/templates/onefile_spec.rb +66 -66
- data/spec/templates/section_spec.rb +144 -144
- data/spec/templates/spec_helper.rb +76 -76
- data/spec/templates/tag_spec.rb +52 -52
- data/spec/templates/template_spec.rb +410 -410
- data/spec/verifier_spec.rb +106 -106
- data/templates/default/class/dot/setup.rb +7 -7
- data/templates/default/class/dot/superklass.erb +2 -2
- data/templates/default/class/html/constructor_details.erb +8 -8
- data/templates/default/class/html/setup.rb +2 -2
- data/templates/default/class/html/subclasses.erb +4 -4
- data/templates/default/class/setup.rb +36 -36
- data/templates/default/class/text/setup.rb +12 -12
- data/templates/default/class/text/subclasses.erb +5 -5
- data/templates/default/constant/text/header.erb +11 -11
- data/templates/default/constant/text/setup.rb +4 -4
- data/templates/default/docstring/html/abstract.erb +4 -4
- data/templates/default/docstring/html/deprecated.erb +1 -1
- data/templates/default/docstring/html/index.erb +5 -5
- data/templates/default/docstring/html/note.erb +6 -6
- data/templates/default/docstring/html/private.erb +4 -4
- data/templates/default/docstring/html/text.erb +1 -1
- data/templates/default/docstring/html/todo.erb +6 -6
- data/templates/default/docstring/setup.rb +52 -52
- data/templates/default/docstring/text/abstract.erb +2 -2
- data/templates/default/docstring/text/deprecated.erb +2 -2
- data/templates/default/docstring/text/index.erb +2 -2
- data/templates/default/docstring/text/note.erb +3 -3
- data/templates/default/docstring/text/private.erb +2 -2
- data/templates/default/docstring/text/text.erb +1 -1
- data/templates/default/docstring/text/todo.erb +3 -3
- data/templates/default/fulldoc/html/css/full_list.css +58 -58
- data/templates/default/fulldoc/html/css/style.css +496 -496
- data/templates/default/fulldoc/html/frames.erb +17 -17
- data/templates/default/fulldoc/html/full_list.erb +37 -37
- data/templates/default/fulldoc/html/full_list_class.erb +2 -2
- data/templates/default/fulldoc/html/full_list_file.erb +7 -7
- data/templates/default/fulldoc/html/full_list_method.erb +10 -10
- data/templates/default/fulldoc/html/js/app.js +314 -292
- data/templates/default/fulldoc/html/js/full_list.js +216 -216
- data/templates/default/fulldoc/html/js/jquery.js +3 -3
- data/templates/default/fulldoc/html/setup.rb +241 -241
- data/templates/default/layout/dot/header.erb +5 -5
- data/templates/default/layout/dot/setup.rb +15 -15
- data/templates/default/layout/html/breadcrumb.erb +11 -11
- data/templates/default/layout/html/files.erb +11 -11
- data/templates/default/layout/html/footer.erb +5 -5
- data/templates/default/layout/html/headers.erb +15 -15
- data/templates/default/layout/html/index.erb +2 -2
- data/templates/default/layout/html/layout.erb +23 -23
- data/templates/default/layout/html/listing.erb +4 -4
- data/templates/default/layout/html/objects.erb +32 -32
- data/templates/default/layout/html/script_setup.erb +4 -4
- data/templates/default/layout/html/search.erb +12 -12
- data/templates/default/layout/html/setup.rb +89 -89
- data/templates/default/method/html/header.erb +16 -16
- data/templates/default/method/setup.rb +4 -4
- data/templates/default/method_details/html/header.erb +2 -2
- data/templates/default/method_details/html/method_signature.erb +24 -24
- data/templates/default/method_details/html/source.erb +9 -9
- data/templates/default/method_details/setup.rb +11 -11
- data/templates/default/method_details/text/header.erb +10 -10
- data/templates/default/method_details/text/method_signature.erb +12 -12
- data/templates/default/method_details/text/setup.rb +11 -11
- data/templates/default/module/dot/child.erb +1 -1
- data/templates/default/module/dot/dependencies.erb +2 -2
- data/templates/default/module/dot/header.erb +6 -6
- data/templates/default/module/dot/info.erb +13 -13
- data/templates/default/module/dot/setup.rb +15 -15
- data/templates/default/module/html/attribute_details.erb +10 -10
- data/templates/default/module/html/attribute_summary.erb +8 -8
- data/templates/default/module/html/box_info.erb +43 -43
- data/templates/default/module/html/children.erb +8 -8
- data/templates/default/module/html/constant_summary.erb +17 -17
- data/templates/default/module/html/defines.erb +2 -2
- data/templates/default/module/html/header.erb +5 -5
- data/templates/default/module/html/inherited_attributes.erb +14 -14
- data/templates/default/module/html/inherited_constants.erb +8 -8
- data/templates/default/module/html/inherited_methods.erb +18 -18
- data/templates/default/module/html/item_summary.erb +40 -40
- data/templates/default/module/html/method_details_list.erb +9 -9
- data/templates/default/module/html/method_summary.erb +13 -13
- data/templates/default/module/html/methodmissing.erb +12 -12
- data/templates/default/module/setup.rb +167 -167
- data/templates/default/module/text/children.erb +9 -9
- data/templates/default/module/text/class_meths_list.erb +7 -7
- data/templates/default/module/text/extends.erb +7 -7
- data/templates/default/module/text/header.erb +7 -7
- data/templates/default/module/text/includes.erb +7 -7
- data/templates/default/module/text/instance_meths_list.erb +7 -7
- data/templates/default/module/text/setup.rb +13 -13
- data/templates/default/onefile/html/files.erb +4 -4
- data/templates/default/onefile/html/headers.erb +6 -6
- data/templates/default/onefile/html/layout.erb +17 -17
- data/templates/default/onefile/html/readme.erb +2 -2
- data/templates/default/onefile/html/setup.rb +62 -62
- data/templates/default/root/dot/child.erb +2 -2
- data/templates/default/root/dot/setup.rb +6 -6
- data/templates/default/root/html/setup.rb +2 -2
- data/templates/default/tags/html/example.erb +10 -10
- data/templates/default/tags/html/index.erb +2 -2
- data/templates/default/tags/html/option.erb +24 -24
- data/templates/default/tags/html/overload.erb +13 -13
- data/templates/default/tags/html/see.erb +7 -7
- data/templates/default/tags/html/tag.erb +20 -20
- data/templates/default/tags/setup.rb +57 -57
- data/templates/default/tags/text/example.erb +12 -12
- data/templates/default/tags/text/index.erb +1 -1
- data/templates/default/tags/text/option.erb +20 -20
- data/templates/default/tags/text/overload.erb +19 -19
- data/templates/default/tags/text/see.erb +11 -11
- data/templates/default/tags/text/tag.erb +13 -13
- data/templates/guide/class/html/setup.rb +2 -2
- data/templates/guide/docstring/html/setup.rb +2 -2
- data/templates/guide/fulldoc/html/css/style.css +108 -108
- data/templates/guide/fulldoc/html/js/app.js +33 -33
- data/templates/guide/fulldoc/html/setup.rb +74 -74
- data/templates/guide/layout/html/layout.erb +81 -81
- data/templates/guide/layout/html/setup.rb +25 -25
- data/templates/guide/method/html/header.erb +17 -17
- data/templates/guide/method/html/setup.rb +22 -22
- data/templates/guide/module/html/header.erb +6 -6
- data/templates/guide/module/html/method_list.erb +4 -4
- data/templates/guide/module/html/setup.rb +27 -27
- data/templates/guide/onefile/html/files.erb +4 -4
- data/templates/guide/onefile/html/setup.rb +6 -6
- data/templates/guide/onefile/html/toc.erb +3 -3
- data/templates/guide/tags/html/setup.rb +9 -9
- data/yard.gemspec +24 -43
- metadata +28 -21
- data/spec/examples.txt +0 -1875
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,15 @@
|
|
1
|
+
This document provides community guidelines for a safe, respectful, productive,
|
2
|
+
and collaborative place for any person who is willing to contribute to the YARD
|
3
|
+
project. It applies to all “collaborative space”, which is defined as community
|
4
|
+
communications channels (such as mailing lists, submitted patches, commit
|
5
|
+
comments, etc.).
|
6
|
+
|
7
|
+
* Participants will be tolerant of opposing views.
|
8
|
+
|
9
|
+
* Participants must ensure that their language and actions are free of personal
|
10
|
+
attacks and disparaging personal remarks.
|
11
|
+
|
12
|
+
* When interpreting the words and actions of others, participants should always
|
13
|
+
assume good intentions.
|
14
|
+
|
15
|
+
* Behaviour which can be reasonably considered harassment will not be tolerated.
|
data/CONTRIBUTING.md
ADDED
@@ -0,0 +1,140 @@
|
|
1
|
+
# Contributing Guide
|
2
|
+
|
3
|
+
## Help YARD Help You!
|
4
|
+
|
5
|
+
**YARD thrives off of the contributions of its users**. This project will gladly
|
6
|
+
review pull requests and issues. This document outlines how to maximize
|
7
|
+
the chance of a reported issue being resolved or pull request being accepted.
|
8
|
+
|
9
|
+
## Code of Conduct
|
10
|
+
|
11
|
+
**All reported issues, pull requests, communication, and code related to YARD**
|
12
|
+
**must follow the [Code of Conduct][code] or they will be moderated immediately**.
|
13
|
+
Please take time to familiarize yourself with the Code of Conduct before
|
14
|
+
you get started. Fundamentally, **you are expected to behave with respect** to all
|
15
|
+
other users.
|
16
|
+
|
17
|
+
## Filing a Bug Report
|
18
|
+
|
19
|
+
**You can submit bug reports on our [GitHub issue tracker][issues]**.
|
20
|
+
|
21
|
+
If you believe you have found a bug, please include a few things in your report:
|
22
|
+
|
23
|
+
1. **A minimal reproduction of the issue**. Providing a huge blob of code is
|
24
|
+
better than nothing, but providing the shortest possible set of instructions
|
25
|
+
is even better. Take out any instructions or code that, when removed, have
|
26
|
+
no effect on the problematic behavior. The easier your bug is to triage and
|
27
|
+
diagnose, the higher up in the priority list it will go. We can do this stuff,
|
28
|
+
but limited time means this may not happen immediately. Make your bug report
|
29
|
+
extremely accessible and you will almost guarantee a quick fix.
|
30
|
+
|
31
|
+
2. **Your environment and relevant versions**. Please include your Ruby,
|
32
|
+
YARD, and system versions (including OS) when reporting a bug. This
|
33
|
+
makes it easier to diagnose problems. If the issue or stack trace
|
34
|
+
includes another library, consider also listing any dependencies
|
35
|
+
that may be affecting the issue. This is where a minimal reproduction
|
36
|
+
case helps a lot.
|
37
|
+
|
38
|
+
3. **Your expected result**. Tell us what you think should happen. This
|
39
|
+
helps us to understand the context of your problem. Many complex features
|
40
|
+
can contain ambiguous usage, and your use case may differ from the
|
41
|
+
intended one. If we know your expectations, we can more easily determine
|
42
|
+
if the behavior is intentional or not.
|
43
|
+
|
44
|
+
Finally, please **DO NOT** submit a report that states a feature simply
|
45
|
+
*"does not work"* without any additional information in the report. Consider
|
46
|
+
the issue from the maintainer's perspective: in order to fix your bug, we
|
47
|
+
need to drill down to the broken line of code, and in order to do this,
|
48
|
+
we must be able to reproduce the issue on our end to find that line of
|
49
|
+
code. The easier we can do this, the quicker your bug gets fixed. Help
|
50
|
+
us help you by providing as much information as you possibly can. We may
|
51
|
+
not have the tools or environment to properly diagnose your issue, so
|
52
|
+
your help may be required to debug the issue.
|
53
|
+
|
54
|
+
Also **consider opening a pull request** to fix the issue yourself if you can.
|
55
|
+
This will likely speed up the fix time significantly. See below for
|
56
|
+
information on how to do this.
|
57
|
+
|
58
|
+
## Asking a Question
|
59
|
+
|
60
|
+
**Questions are accepted on [GitHub issues][issues], but consider signing up**
|
61
|
+
**for the [YARD mailing list][ml]** and asking it there so that we can organize
|
62
|
+
issues appropriately. You can also hop onto IRC (irc.freenode.net / #yard)
|
63
|
+
for quick questions.
|
64
|
+
|
65
|
+
## Asking for a Feature
|
66
|
+
|
67
|
+
**YARD does not currently accept feature requests filed as GitHub issues**. If
|
68
|
+
you are looking to have a feature implemented into YARD, consider doing this
|
69
|
+
yourself and [submitting a pull request][pr] (PR) with your work. If the work
|
70
|
+
required is involved, consider starting a discussion on the [mailing list][ml]
|
71
|
+
or opening an issue to ask a question; we will be happy to have a conversation
|
72
|
+
and let you know if the feature would be considered. They usually are, but
|
73
|
+
it might be prudent to ask first!
|
74
|
+
|
75
|
+
Please do not fret if your feature request gets closed immediately. We do this
|
76
|
+
to keep our issue tracker clean. **Closing an issue does not mean it would not**
|
77
|
+
**be accepted as a pull request**. If the feature would not be accepted as a
|
78
|
+
PR, this will be communicated in the closed issue.
|
79
|
+
|
80
|
+
## Making a Change via Pull Request
|
81
|
+
|
82
|
+
**You can also submit pull requests on our [GitHub issue tracker][issues]**.
|
83
|
+
|
84
|
+
If you've been working on a patch or feature that you want in YARD, here are
|
85
|
+
some tips to ensure the quickest turnaround time on getting it merged in:
|
86
|
+
|
87
|
+
1. **Keep your changes small**. If your feature is large, consider splitting
|
88
|
+
it up into smaller portions and submit pull requests for each component
|
89
|
+
individually. Feel free to describe this in your first PR or on the
|
90
|
+
mailing list, but note that it will be much easier to review changes
|
91
|
+
if they affect smaller portions of code at a time.
|
92
|
+
|
93
|
+
2. **Keep commits brief and clean**: YARD uses Git and tries to maintain a
|
94
|
+
clean repository. Please ensure that you use [commit conventions][commit]
|
95
|
+
to make things nice and neat both in the description and commit history.
|
96
|
+
Specifically, consider squashing commits if you have partial or complete
|
97
|
+
reverts of code. Each commit should provide an atomic change that moves
|
98
|
+
the project forwards, not back. Any changes that only fix other parts of
|
99
|
+
your PR should be hidden from the commit history.
|
100
|
+
|
101
|
+
3. **Follow our coding conventions**. YARD uses typical Ruby source formatting,
|
102
|
+
though it occasionally has minor differences with other projects you may
|
103
|
+
have seen. Please look through a few files (at least the file you are
|
104
|
+
editing) to ensure that you are consistent in the formatting your PR is
|
105
|
+
using.
|
106
|
+
|
107
|
+
4. **Make sure you have tests**. Not all changes require tests, but if your
|
108
|
+
changes involve code, you should consider adding at least one new test
|
109
|
+
case for your change (and ideally a couple of tests). This will add
|
110
|
+
confidence when reviewing and will make accepting the change much easier.
|
111
|
+
|
112
|
+
5. **Make sure ALL the tests pass**. YARD has a fairly large suite of tests.
|
113
|
+
Please make sure you can run all of the tests (`bundle exec rake`) prior
|
114
|
+
to submitting your PR. Please also remember that YARD supports a number
|
115
|
+
of environments, including OS X, Linux, Windows, and a number of older
|
116
|
+
Ruby versions (1.8+), so if you can test under these environments, that
|
117
|
+
helps (but is not required). At the very least, be aware of this fact
|
118
|
+
when submitting code.
|
119
|
+
|
120
|
+
If your change is large, consider starting a discussion on the [mailing list][ml]
|
121
|
+
or opening an issue to ask a question; we will be happy to have a conversation
|
122
|
+
and let you know if the feature would be considered. They usually are, but
|
123
|
+
it might be prudent to ask first!
|
124
|
+
|
125
|
+
## Maintainers
|
126
|
+
|
127
|
+
**Interested in helping to maintain YARD? Email [lsegal@soen.ca][mail]** for more
|
128
|
+
information. Offering to be a project maintainer is an important contribution
|
129
|
+
to open source software, and your work will be highly valued in the community.
|
130
|
+
If you have been a contributor, consider being a member of the core team to
|
131
|
+
help handle day-to-day operations, such as releases, bug fixes, and triage.
|
132
|
+
You can do some of this as a non-maintainer too, but if you like this project,
|
133
|
+
we can always use more hands on deck!
|
134
|
+
|
135
|
+
[code]: https://github.com/lsegal/yard/blob/master/CODE_OF_CONDUCT.md
|
136
|
+
[issues]: http://github.com/lsegal/yard/issues
|
137
|
+
[commit]: http://chris.beams.io/posts/git-commit/
|
138
|
+
[pr]: https://help.github.com/articles/using-pull-requests/
|
139
|
+
[ml]: https://groups.google.com/forum/#!forum/yardoc
|
140
|
+
[mail]: mailto:lsegal@soen.ca
|
data/Dockerfile.samus
ADDED
@@ -0,0 +1,28 @@
|
|
1
|
+
FROM lsegal/samus:latest as samus
|
2
|
+
|
3
|
+
FROM ruby:2
|
4
|
+
ARG VERSION
|
5
|
+
ENV VERSION=${VERSION}
|
6
|
+
WORKDIR /github/lsegal/yard
|
7
|
+
ENTRYPOINT samus publish release-v${VERSION}.tar.gz
|
8
|
+
|
9
|
+
# Prepare credential config
|
10
|
+
RUN mkdir -p ~/.ssh
|
11
|
+
RUN echo "Host *" > ~/.ssh/config
|
12
|
+
RUN echo " StrictHostKeyChecking no" >> ~/.ssh/config
|
13
|
+
RUN chmod 400 ~/.ssh/config
|
14
|
+
COPY ./.samusprep/.samus /root/.samus
|
15
|
+
COPY ./.samusprep/.gitconfig /root/.gitconfig
|
16
|
+
|
17
|
+
# Setup Samus
|
18
|
+
ENV PATH=$PATH:/samus/bin
|
19
|
+
COPY --from=samus /samus /samus
|
20
|
+
|
21
|
+
# Install gems
|
22
|
+
ENV BUNDLE_PATH=/var/gems
|
23
|
+
COPY Gemfile /github/lsegal/yard
|
24
|
+
RUN bundle
|
25
|
+
|
26
|
+
# Run build
|
27
|
+
COPY . /github/lsegal/yard
|
28
|
+
RUN samus build --skip-restore ${VERSION}
|
data/Gemfile
ADDED
@@ -0,0 +1,32 @@
|
|
1
|
+
# frozen_string_literal: true
|
2
|
+
source 'https://rubygems.org'
|
3
|
+
|
4
|
+
group :development do
|
5
|
+
gem 'rspec'
|
6
|
+
gem 'rake'
|
7
|
+
gem 'rdoc'
|
8
|
+
gem 'json'
|
9
|
+
gem 'simplecov'
|
10
|
+
gem 'samus', '~> 3.0.8', :require => false
|
11
|
+
gem 'coveralls', :require => false
|
12
|
+
end
|
13
|
+
|
14
|
+
group :asciidoc do
|
15
|
+
gem 'asciidoctor'
|
16
|
+
end
|
17
|
+
|
18
|
+
group :markdown do
|
19
|
+
gem 'redcarpet', :platforms => [:ruby]
|
20
|
+
end
|
21
|
+
|
22
|
+
group :textile do
|
23
|
+
gem 'RedCloth', :platforms => [:ruby]
|
24
|
+
end
|
25
|
+
|
26
|
+
group :server do
|
27
|
+
gem 'rack'
|
28
|
+
end
|
29
|
+
|
30
|
+
group :i18n do
|
31
|
+
gem 'gettext'
|
32
|
+
end
|
data/LEGAL
CHANGED
@@ -1,66 +1,66 @@
|
|
1
|
-
LEGAL NOTICE INFORMATION
|
2
|
-
------------------------
|
3
|
-
|
4
|
-
All the files in this distribution are covered under either the MIT
|
5
|
-
license (see the file LICENSE) except some files mentioned below.
|
6
|
-
|
7
|
-
lib/parser/ruby/legacy/ruby_lex.rb:
|
8
|
-
|
9
|
-
This file is under the Ruby license. YARD uses a modified version of it.
|
10
|
-
|
11
|
-
Ruby is copyrighted free software by Yukihiro Matsumoto <matz@netlab.jp>.
|
12
|
-
You can redistribute it and/or modify it under either the terms of the GPL
|
13
|
-
version 2 (see the file GPL), or the conditions below:
|
14
|
-
|
15
|
-
1. You may make and give away verbatim copies of the source form of the
|
16
|
-
software without restriction, provided that you duplicate all of the
|
17
|
-
original copyright notices and associated disclaimers.
|
18
|
-
|
19
|
-
2. You may modify your copy of the software in any way, provided that
|
20
|
-
you do at least ONE of the following:
|
21
|
-
|
22
|
-
a) place your modifications in the Public Domain or otherwise
|
23
|
-
make them Freely Available, such as by posting said
|
24
|
-
modifications to Usenet or an equivalent medium, or by allowing
|
25
|
-
the author to include your modifications in the software.
|
26
|
-
|
27
|
-
b) use the modified software only within your corporation or
|
28
|
-
organization.
|
29
|
-
|
30
|
-
c) give non-standard binaries non-standard names, with
|
31
|
-
instructions on where to get the original software distribution.
|
32
|
-
|
33
|
-
d) make other distribution arrangements with the author.
|
34
|
-
|
35
|
-
3. You may distribute the software in object code or binary form,
|
36
|
-
provided that you do at least ONE of the following:
|
37
|
-
|
38
|
-
a) distribute the binaries and library files of the software,
|
39
|
-
together with instructions (in the manual page or equivalent)
|
40
|
-
on where to get the original distribution.
|
41
|
-
|
42
|
-
b) accompany the distribution with the machine-readable source of
|
43
|
-
the software.
|
44
|
-
|
45
|
-
c) give non-standard binaries non-standard names, with
|
46
|
-
instructions on where to get the original software distribution.
|
47
|
-
|
48
|
-
d) make other distribution arrangements with the author.
|
49
|
-
|
50
|
-
4. You may modify and include the part of the software into any other
|
51
|
-
software (possibly commercial). But some files in the distribution
|
52
|
-
are not written by the author, so that they are not under these terms.
|
53
|
-
|
54
|
-
For the list of those files and their copying conditions, see the
|
55
|
-
file LEGAL.
|
56
|
-
|
57
|
-
5. The scripts and library files supplied as input to or produced as
|
58
|
-
output from the software do not automatically fall under the
|
59
|
-
copyright of the software, but belong to whomever generated them,
|
60
|
-
and may be sold commercially, and may be aggregated with this
|
61
|
-
software.
|
62
|
-
|
63
|
-
6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
|
64
|
-
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
|
65
|
-
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
66
|
-
PURPOSE.
|
1
|
+
LEGAL NOTICE INFORMATION
|
2
|
+
------------------------
|
3
|
+
|
4
|
+
All the files in this distribution are covered under either the MIT
|
5
|
+
license (see the file LICENSE) except some files mentioned below.
|
6
|
+
|
7
|
+
lib/parser/ruby/legacy/ruby_lex.rb:
|
8
|
+
|
9
|
+
This file is under the Ruby license. YARD uses a modified version of it.
|
10
|
+
|
11
|
+
Ruby is copyrighted free software by Yukihiro Matsumoto <matz@netlab.jp>.
|
12
|
+
You can redistribute it and/or modify it under either the terms of the GPL
|
13
|
+
version 2 (see the file GPL), or the conditions below:
|
14
|
+
|
15
|
+
1. You may make and give away verbatim copies of the source form of the
|
16
|
+
software without restriction, provided that you duplicate all of the
|
17
|
+
original copyright notices and associated disclaimers.
|
18
|
+
|
19
|
+
2. You may modify your copy of the software in any way, provided that
|
20
|
+
you do at least ONE of the following:
|
21
|
+
|
22
|
+
a) place your modifications in the Public Domain or otherwise
|
23
|
+
make them Freely Available, such as by posting said
|
24
|
+
modifications to Usenet or an equivalent medium, or by allowing
|
25
|
+
the author to include your modifications in the software.
|
26
|
+
|
27
|
+
b) use the modified software only within your corporation or
|
28
|
+
organization.
|
29
|
+
|
30
|
+
c) give non-standard binaries non-standard names, with
|
31
|
+
instructions on where to get the original software distribution.
|
32
|
+
|
33
|
+
d) make other distribution arrangements with the author.
|
34
|
+
|
35
|
+
3. You may distribute the software in object code or binary form,
|
36
|
+
provided that you do at least ONE of the following:
|
37
|
+
|
38
|
+
a) distribute the binaries and library files of the software,
|
39
|
+
together with instructions (in the manual page or equivalent)
|
40
|
+
on where to get the original distribution.
|
41
|
+
|
42
|
+
b) accompany the distribution with the machine-readable source of
|
43
|
+
the software.
|
44
|
+
|
45
|
+
c) give non-standard binaries non-standard names, with
|
46
|
+
instructions on where to get the original software distribution.
|
47
|
+
|
48
|
+
d) make other distribution arrangements with the author.
|
49
|
+
|
50
|
+
4. You may modify and include the part of the software into any other
|
51
|
+
software (possibly commercial). But some files in the distribution
|
52
|
+
are not written by the author, so that they are not under these terms.
|
53
|
+
|
54
|
+
For the list of those files and their copying conditions, see the
|
55
|
+
file LEGAL.
|
56
|
+
|
57
|
+
5. The scripts and library files supplied as input to or produced as
|
58
|
+
output from the software do not automatically fall under the
|
59
|
+
copyright of the software, but belong to whomever generated them,
|
60
|
+
and may be sold commercially, and may be aggregated with this
|
61
|
+
software.
|
62
|
+
|
63
|
+
6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
|
64
|
+
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
|
65
|
+
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
66
|
+
PURPOSE.
|
data/LICENSE
CHANGED
@@ -1,22 +1,22 @@
|
|
1
|
-
Copyright (c) 2007-2018 Loren Segal
|
2
|
-
|
3
|
-
Permission is hereby granted, free of charge, to any person
|
4
|
-
obtaining a copy of this software and associated documentation
|
5
|
-
files (the "Software"), to deal in the Software without
|
6
|
-
restriction, including without limitation the rights to use,
|
7
|
-
copy, modify, merge, publish, distribute, sublicense, and/or sell
|
8
|
-
copies of the Software, and to permit persons to whom the
|
9
|
-
Software is furnished to do so, subject to the following
|
10
|
-
conditions:
|
11
|
-
|
12
|
-
The above copyright notice and this permission notice shall be
|
13
|
-
included in all copies or substantial portions of the Software.
|
14
|
-
|
15
|
-
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
16
|
-
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
|
17
|
-
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
|
18
|
-
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
|
19
|
-
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
|
20
|
-
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
|
21
|
-
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
|
22
|
-
OTHER DEALINGS IN THE SOFTWARE.
|
1
|
+
Copyright (c) 2007-2018 Loren Segal
|
2
|
+
|
3
|
+
Permission is hereby granted, free of charge, to any person
|
4
|
+
obtaining a copy of this software and associated documentation
|
5
|
+
files (the "Software"), to deal in the Software without
|
6
|
+
restriction, including without limitation the rights to use,
|
7
|
+
copy, modify, merge, publish, distribute, sublicense, and/or sell
|
8
|
+
copies of the Software, and to permit persons to whom the
|
9
|
+
Software is furnished to do so, subject to the following
|
10
|
+
conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be
|
13
|
+
included in all copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
16
|
+
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
|
17
|
+
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
|
18
|
+
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
|
19
|
+
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
|
20
|
+
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
|
21
|
+
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
|
22
|
+
OTHER DEALINGS IN THE SOFTWARE.
|
data/README.md
CHANGED
@@ -1,328 +1,330 @@
|
|
1
|
-
# YARD: Yay! A Ruby Documentation Tool
|
2
|
-
|
3
|
-
[![Homepage](http://img.shields.io/badge/home-yardoc.org-blue.svg)](http://yardoc.org)
|
4
|
-
[![GitHub](http://img.shields.io/badge/github-lsegal/yard-blue.svg)](http://github.com/lsegal/yard)
|
5
|
-
[![Documentation](http://img.shields.io/badge/docs-rdoc.info-blue.svg)](http://rubydoc.org/gems/yard/frames)
|
6
|
-
|
7
|
-
[![Gem Version](https://badge.fury.io/rb/yard.svg)](http://github.com/lsegal/yard/releases)
|
8
|
-
[![Build Status](https://travis-ci.org/lsegal/yard.svg?branch=master)](https://travis-ci.org/lsegal/yard)
|
9
|
-
[![Coverage Status](https://coveralls.io/repos/github/lsegal/yard/badge.svg)](https://coveralls.io/github/lsegal/yard)
|
10
|
-
[![License](http://img.shields.io/badge/license-MIT-yellowgreen.svg)](#license)
|
11
|
-
|
12
|
-
## Synopsis
|
13
|
-
|
14
|
-
YARD is a documentation generation tool for the Ruby programming language.
|
15
|
-
It enables the user to generate consistent, usable documentation that can be
|
16
|
-
exported to a number of formats very easily, and also supports extending for
|
17
|
-
custom Ruby constructs such as custom class level definitions. Below is a
|
18
|
-
summary of some of YARD's notable features.
|
19
|
-
|
20
|
-
|
21
|
-
## Feature List
|
22
|
-
|
23
|
-
**1. RDoc/SimpleMarkup Formatting Compatibility**: YARD is made to be compatible
|
24
|
-
with RDoc formatting. In fact, YARD does no processing on RDoc documentation
|
25
|
-
strings, and leaves this up to the output generation tool to decide how to
|
26
|
-
render the documentation.
|
27
|
-
|
28
|
-
**2. Yardoc Meta-tag Formatting Like Python, Java, Objective-C and other languages**:
|
29
|
-
YARD uses a '@tag' style definition syntax for meta tags alongside regular code
|
30
|
-
documentation. These tags should be able to happily sit side by side RDoc formatted
|
31
|
-
documentation, but provide a much more consistent and usable way to describe
|
32
|
-
important information about objects, such as what parameters they take and what types
|
33
|
-
they are expected to be, what type a method should return, what exceptions it can
|
34
|
-
raise, if it is deprecated, etc.. It also allows information to be better (and more
|
35
|
-
consistently) organized during the output generation phase. You can find a list
|
36
|
-
of tags in the {file:docs/Tags.md#taglist Tags.md} file.
|
37
|
-
|
38
|
-
YARD also supports an optional "types" declarations for certain tags.
|
39
|
-
This allows the developer to document type signatures for ruby methods and
|
40
|
-
parameters in a non intrusive but helpful and consistent manner. Instead of
|
41
|
-
describing this data in the body of the description, a developer may formally
|
42
|
-
declare the parameter or return type(s) in a single line. Consider the
|
43
|
-
following method documented with YARD formatting:
|
44
|
-
|
45
|
-
```ruby
|
46
|
-
# Reverses the contents of a String or IO object.
|
47
|
-
#
|
48
|
-
# @param contents [String, #read] the contents to reverse
|
49
|
-
# @return [String] the contents reversed lexically
|
50
|
-
def reverse(contents)
|
51
|
-
contents = contents.read if contents.respond_to? :read
|
52
|
-
contents.reverse
|
53
|
-
end
|
54
|
-
```
|
55
|
-
|
56
|
-
With the above @param tag, we learn that the contents parameter can either be
|
57
|
-
a String or any object that responds to the 'read' method, which is more
|
58
|
-
powerful than the textual description, which says it should be an IO object.
|
59
|
-
This also informs the developer that they should expect to receive a String
|
60
|
-
object returned by the method, and although this may be obvious for a
|
61
|
-
'reverse' method, it becomes very useful when the method name may not be as
|
62
|
-
descriptive.
|
63
|
-
|
64
|
-
**3. Custom Constructs and Extensibility of YARD**: YARD is designed to be
|
65
|
-
extended and customized by plugins. Take for instance the scenario where you
|
66
|
-
need to document the following code:
|
67
|
-
|
68
|
-
```ruby
|
69
|
-
class List
|
70
|
-
# Sets the publisher name for the list.
|
71
|
-
cattr_accessor :publisher
|
72
|
-
end
|
73
|
-
```
|
74
|
-
|
75
|
-
This custom declaration provides dynamically generated code that is hard for a
|
76
|
-
documentation tool to properly document without help from the developer. To
|
77
|
-
ease the pains of manually documenting the procedure, YARD can be extended by
|
78
|
-
the developer to handle the `cattr_accessor` construct and automatically create
|
79
|
-
an attribute on the class with the associated documentation. This makes
|
80
|
-
documenting external API's, especially dynamic ones, a lot more consistent for
|
81
|
-
consumption by the users.
|
82
|
-
|
83
|
-
YARD is also designed for extensibility everywhere else, allowing you to add
|
84
|
-
support for new programming languages, new data structures and even where/how
|
85
|
-
data is stored.
|
86
|
-
|
87
|
-
**4. Raw Data Output**: YARD also outputs documented objects as raw data (the
|
88
|
-
dumped Namespace) which can be reloaded to do generation at a later date, or
|
89
|
-
even auditing on code. This means that any developer can use the raw data to
|
90
|
-
perform output generation for any custom format, such as YAML, for instance.
|
91
|
-
While YARD plans to support XHTML style documentation output as well as
|
92
|
-
command line (text based) and possibly XML, this may still be useful for those
|
93
|
-
who would like to reap the benefits of YARD's processing in other forms, such
|
94
|
-
as throwing all the documentation into a database. Another useful way of
|
95
|
-
exploiting this raw data format would be to write tools that can auto generate
|
96
|
-
test cases, for example, or show possible unhandled exceptions in code.
|
97
|
-
|
98
|
-
**5. Local Documentation Server**: YARD can serve documentation for projects
|
99
|
-
or installed gems (similar to `gem server`) with the added benefit of dynamic
|
100
|
-
searching, as well as live reloading. Using the live reload feature, you can
|
101
|
-
document your code and immediately preview the results by refreshing the page;
|
102
|
-
YARD will do all the work in re-generating the HTML. This makes writing
|
103
|
-
documentation a much faster process.
|
104
|
-
|
105
|
-
|
106
|
-
## Installing
|
107
|
-
|
108
|
-
To install YARD, use the following command:
|
109
|
-
|
110
|
-
```sh
|
111
|
-
$ gem install yard
|
112
|
-
```
|
113
|
-
|
114
|
-
(Add `sudo` if you're installing under a POSIX system as root)
|
115
|
-
|
116
|
-
Alternatively, if you've checked the source out directly, you can call
|
117
|
-
`rake install` from the root project directory.
|
118
|
-
|
119
|
-
**Important Note for Debian/Ubuntu users:** there's a possible chance your Ruby
|
120
|
-
install lacks RDoc, which is occasionally used by YARD to convert markup to HTML.
|
121
|
-
If running `which rdoc` turns up empty, install RDoc by issuing:
|
122
|
-
|
123
|
-
```sh
|
124
|
-
$ sudo apt-get install rdoc
|
125
|
-
```
|
126
|
-
|
127
|
-
|
128
|
-
## Usage
|
129
|
-
|
130
|
-
There are a couple of ways to use YARD. The first is via command-line, and the
|
131
|
-
second is the Rake task.
|
132
|
-
|
133
|
-
**1. yard Command-line Tool**
|
134
|
-
|
135
|
-
YARD comes packaged with a executable named `yard` which can control the many
|
136
|
-
functions of YARD, including generating documentation, graphs running the
|
137
|
-
YARD server, and so on. To view a list of available YARD commands, type:
|
138
|
-
|
139
|
-
```sh
|
140
|
-
$ yard --help
|
141
|
-
```
|
142
|
-
|
143
|
-
Plugins can also add commands to the `yard` executable to provide extra
|
144
|
-
functionality.
|
145
|
-
|
146
|
-
### Generating Documentation
|
147
|
-
|
148
|
-
<span class="note">The `yardoc` executable is a shortcut for `yard doc`.</span>
|
149
|
-
|
150
|
-
The most common command you will probably use is `yard doc`, or `yardoc`. You
|
151
|
-
can type `yardoc --help` to see the options that YARD provides, but the
|
152
|
-
easiest way to generate docs for your code is to simply type `yardoc` in your
|
153
|
-
project root. This will assume your files are
|
154
|
-
located in the `lib/` directory. If they are located elsewhere, you can specify
|
155
|
-
paths and globs from the commandline via:
|
156
|
-
|
157
|
-
```sh
|
158
|
-
$ yardoc 'lib/**/*.rb' 'app/**/*.rb' ...etc...
|
159
|
-
```
|
160
|
-
|
161
|
-
The tool will generate a `.yardoc` file which will store the cached database
|
162
|
-
of your source code and documentation. If you want to re-generate your docs
|
163
|
-
with another template you can simply use the `--use-cache` (or -c)
|
164
|
-
option to speed up the generation process by skipping source parsing.
|
165
|
-
|
166
|
-
YARD will by default only document code in your public visibility. You can
|
167
|
-
document your protected and private code by adding `--protected` or
|
168
|
-
`--private` to the option switches. In addition, you can add `--no-private`
|
169
|
-
to also ignore any object that has the `@private` meta-tag. This is similar
|
170
|
-
to RDoc's ":nodoc:" behaviour, though the distinction is important. RDoc
|
171
|
-
implies that the object with :nodoc: would not be documented, whereas
|
172
|
-
YARD still recommends documenting private objects for the private API (for
|
173
|
-
maintainer/developer consumption).
|
174
|
-
|
175
|
-
You can also add extra informative files (README, LICENSE) by separating
|
176
|
-
the globs and the filenames with '-'.
|
177
|
-
|
178
|
-
```sh
|
179
|
-
$ yardoc 'app/**/*.rb' - README LICENSE FAQ
|
180
|
-
```
|
181
|
-
|
182
|
-
If no globs precede the '-' argument, the default glob (`lib/**/*.rb`) is
|
183
|
-
used:
|
184
|
-
|
185
|
-
```sh
|
186
|
-
$ yardoc - README LICENSE FAQ
|
187
|
-
```
|
188
|
-
|
189
|
-
Note that the README file can be specified with its own `--readme` switch.
|
190
|
-
|
191
|
-
You can also add a `.yardopts` file to your project directory which lists
|
192
|
-
the switches separated by whitespace (newlines or space) to pass to yardoc
|
193
|
-
whenever it is run. A full overview of the `.yardopts` file can be found in
|
194
|
-
{YARD::CLI::Yardoc}.
|
195
|
-
|
196
|
-
### Queries
|
197
|
-
|
198
|
-
The `yardoc` tool also supports a `--query` argument to only include objects
|
199
|
-
that match a certain data or meta-data query. The query syntax is Ruby, though
|
200
|
-
a few shortcuts are available. For instance, to document only objects that have
|
201
|
-
an "@api" tag with the value "public", all of the following syntaxes would give
|
202
|
-
the same result:
|
203
|
-
|
204
|
-
```sh
|
205
|
-
--query '@api.text == "public"'
|
206
|
-
--query 'object.has_tag?(:api) && object.tag(:api).text == "public"'
|
207
|
-
--query 'has_tag?(:api) && tag(:api).text == "public"'
|
208
|
-
```
|
209
|
-
|
210
|
-
Note that the "@tag" syntax returns the first tag named "tag" on the object.
|
211
|
-
To return the array of all tags named "tag", use "@@tag".
|
212
|
-
|
213
|
-
Multiple `--query` arguments are allowed in the command line parameters. The
|
214
|
-
following two lines both check for the existence of a return and param tag:
|
215
|
-
|
216
|
-
```sh
|
217
|
-
--query '@return' --query '@param'
|
218
|
-
--query '@return && @param'
|
219
|
-
```
|
220
|
-
|
221
|
-
For more information about the query syntax, see the {YARD::Verifier} class.
|
222
|
-
|
223
|
-
**2. Rake Task**
|
224
|
-
|
225
|
-
The second most obvious is to generate docs via a Rake task. You can do this by
|
226
|
-
adding the following to your `Rakefile`:
|
227
|
-
|
228
|
-
```ruby
|
229
|
-
|
230
|
-
|
231
|
-
|
232
|
-
t.
|
233
|
-
|
234
|
-
|
235
|
-
|
236
|
-
|
237
|
-
|
238
|
-
|
239
|
-
|
240
|
-
|
241
|
-
|
242
|
-
|
243
|
-
|
244
|
-
|
245
|
-
```
|
246
|
-
|
247
|
-
|
248
|
-
|
249
|
-
|
250
|
-
|
251
|
-
|
252
|
-
|
253
|
-
|
254
|
-
|
255
|
-
|
256
|
-
|
257
|
-
|
258
|
-
|
259
|
-
|
260
|
-
|
261
|
-
|
262
|
-
|
263
|
-
|
264
|
-
|
265
|
-
|
266
|
-
```
|
267
|
-
|
268
|
-
|
269
|
-
|
270
|
-
|
271
|
-
|
272
|
-
|
273
|
-
|
274
|
-
|
275
|
-
|
276
|
-
|
277
|
-
|
278
|
-
```
|
279
|
-
|
280
|
-
|
281
|
-
|
282
|
-
|
283
|
-
|
284
|
-
|
285
|
-
|
286
|
-
|
287
|
-
|
288
|
-
|
289
|
-
|
290
|
-
|
291
|
-
|
292
|
-
|
293
|
-
|
294
|
-
|
295
|
-
|
296
|
-
```
|
297
|
-
|
298
|
-
|
299
|
-
|
300
|
-
|
301
|
-
|
302
|
-
|
303
|
-
|
304
|
-
|
305
|
-
|
306
|
-
|
307
|
-
|
308
|
-
|
309
|
-
|
310
|
-
|
311
|
-
|
312
|
-
|
313
|
-
|
314
|
-
|
315
|
-
|
316
|
-
```
|
317
|
-
|
318
|
-
|
319
|
-
|
320
|
-
|
321
|
-
|
322
|
-
|
323
|
-
|
324
|
-
|
325
|
-
|
326
|
-
|
327
|
-
|
328
|
-
|
1
|
+
# YARD: Yay! A Ruby Documentation Tool
|
2
|
+
|
3
|
+
[![Homepage](http://img.shields.io/badge/home-yardoc.org-blue.svg)](http://yardoc.org)
|
4
|
+
[![GitHub](http://img.shields.io/badge/github-lsegal/yard-blue.svg)](http://github.com/lsegal/yard)
|
5
|
+
[![Documentation](http://img.shields.io/badge/docs-rdoc.info-blue.svg)](http://rubydoc.org/gems/yard/frames)
|
6
|
+
|
7
|
+
[![Gem Version](https://badge.fury.io/rb/yard.svg)](http://github.com/lsegal/yard/releases)
|
8
|
+
[![Build Status](https://travis-ci.org/lsegal/yard.svg?branch=master)](https://travis-ci.org/lsegal/yard)
|
9
|
+
[![Coverage Status](https://coveralls.io/repos/github/lsegal/yard/badge.svg)](https://coveralls.io/github/lsegal/yard)
|
10
|
+
[![License](http://img.shields.io/badge/license-MIT-yellowgreen.svg)](#license)
|
11
|
+
|
12
|
+
## Synopsis
|
13
|
+
|
14
|
+
YARD is a documentation generation tool for the Ruby programming language.
|
15
|
+
It enables the user to generate consistent, usable documentation that can be
|
16
|
+
exported to a number of formats very easily, and also supports extending for
|
17
|
+
custom Ruby constructs such as custom class level definitions. Below is a
|
18
|
+
summary of some of YARD's notable features.
|
19
|
+
|
20
|
+
|
21
|
+
## Feature List
|
22
|
+
|
23
|
+
**1. RDoc/SimpleMarkup Formatting Compatibility**: YARD is made to be compatible
|
24
|
+
with RDoc formatting. In fact, YARD does no processing on RDoc documentation
|
25
|
+
strings, and leaves this up to the output generation tool to decide how to
|
26
|
+
render the documentation.
|
27
|
+
|
28
|
+
**2. Yardoc Meta-tag Formatting Like Python, Java, Objective-C and other languages**:
|
29
|
+
YARD uses a '@tag' style definition syntax for meta tags alongside regular code
|
30
|
+
documentation. These tags should be able to happily sit side by side RDoc formatted
|
31
|
+
documentation, but provide a much more consistent and usable way to describe
|
32
|
+
important information about objects, such as what parameters they take and what types
|
33
|
+
they are expected to be, what type a method should return, what exceptions it can
|
34
|
+
raise, if it is deprecated, etc.. It also allows information to be better (and more
|
35
|
+
consistently) organized during the output generation phase. You can find a list
|
36
|
+
of tags in the {file:docs/Tags.md#taglist Tags.md} file.
|
37
|
+
|
38
|
+
YARD also supports an optional "types" declarations for certain tags.
|
39
|
+
This allows the developer to document type signatures for ruby methods and
|
40
|
+
parameters in a non intrusive but helpful and consistent manner. Instead of
|
41
|
+
describing this data in the body of the description, a developer may formally
|
42
|
+
declare the parameter or return type(s) in a single line. Consider the
|
43
|
+
following method documented with YARD formatting:
|
44
|
+
|
45
|
+
```ruby
|
46
|
+
# Reverses the contents of a String or IO object.
|
47
|
+
#
|
48
|
+
# @param contents [String, #read] the contents to reverse
|
49
|
+
# @return [String] the contents reversed lexically
|
50
|
+
def reverse(contents)
|
51
|
+
contents = contents.read if contents.respond_to? :read
|
52
|
+
contents.reverse
|
53
|
+
end
|
54
|
+
```
|
55
|
+
|
56
|
+
With the above @param tag, we learn that the contents parameter can either be
|
57
|
+
a String or any object that responds to the 'read' method, which is more
|
58
|
+
powerful than the textual description, which says it should be an IO object.
|
59
|
+
This also informs the developer that they should expect to receive a String
|
60
|
+
object returned by the method, and although this may be obvious for a
|
61
|
+
'reverse' method, it becomes very useful when the method name may not be as
|
62
|
+
descriptive.
|
63
|
+
|
64
|
+
**3. Custom Constructs and Extensibility of YARD**: YARD is designed to be
|
65
|
+
extended and customized by plugins. Take for instance the scenario where you
|
66
|
+
need to document the following code:
|
67
|
+
|
68
|
+
```ruby
|
69
|
+
class List
|
70
|
+
# Sets the publisher name for the list.
|
71
|
+
cattr_accessor :publisher
|
72
|
+
end
|
73
|
+
```
|
74
|
+
|
75
|
+
This custom declaration provides dynamically generated code that is hard for a
|
76
|
+
documentation tool to properly document without help from the developer. To
|
77
|
+
ease the pains of manually documenting the procedure, YARD can be extended by
|
78
|
+
the developer to handle the `cattr_accessor` construct and automatically create
|
79
|
+
an attribute on the class with the associated documentation. This makes
|
80
|
+
documenting external API's, especially dynamic ones, a lot more consistent for
|
81
|
+
consumption by the users.
|
82
|
+
|
83
|
+
YARD is also designed for extensibility everywhere else, allowing you to add
|
84
|
+
support for new programming languages, new data structures and even where/how
|
85
|
+
data is stored.
|
86
|
+
|
87
|
+
**4. Raw Data Output**: YARD also outputs documented objects as raw data (the
|
88
|
+
dumped Namespace) which can be reloaded to do generation at a later date, or
|
89
|
+
even auditing on code. This means that any developer can use the raw data to
|
90
|
+
perform output generation for any custom format, such as YAML, for instance.
|
91
|
+
While YARD plans to support XHTML style documentation output as well as
|
92
|
+
command line (text based) and possibly XML, this may still be useful for those
|
93
|
+
who would like to reap the benefits of YARD's processing in other forms, such
|
94
|
+
as throwing all the documentation into a database. Another useful way of
|
95
|
+
exploiting this raw data format would be to write tools that can auto generate
|
96
|
+
test cases, for example, or show possible unhandled exceptions in code.
|
97
|
+
|
98
|
+
**5. Local Documentation Server**: YARD can serve documentation for projects
|
99
|
+
or installed gems (similar to `gem server`) with the added benefit of dynamic
|
100
|
+
searching, as well as live reloading. Using the live reload feature, you can
|
101
|
+
document your code and immediately preview the results by refreshing the page;
|
102
|
+
YARD will do all the work in re-generating the HTML. This makes writing
|
103
|
+
documentation a much faster process.
|
104
|
+
|
105
|
+
|
106
|
+
## Installing
|
107
|
+
|
108
|
+
To install YARD, use the following command:
|
109
|
+
|
110
|
+
```sh
|
111
|
+
$ gem install yard
|
112
|
+
```
|
113
|
+
|
114
|
+
(Add `sudo` if you're installing under a POSIX system as root)
|
115
|
+
|
116
|
+
Alternatively, if you've checked the source out directly, you can call
|
117
|
+
`rake install` from the root project directory.
|
118
|
+
|
119
|
+
**Important Note for Debian/Ubuntu users:** there's a possible chance your Ruby
|
120
|
+
install lacks RDoc, which is occasionally used by YARD to convert markup to HTML.
|
121
|
+
If running `which rdoc` turns up empty, install RDoc by issuing:
|
122
|
+
|
123
|
+
```sh
|
124
|
+
$ sudo apt-get install rdoc
|
125
|
+
```
|
126
|
+
|
127
|
+
|
128
|
+
## Usage
|
129
|
+
|
130
|
+
There are a couple of ways to use YARD. The first is via command-line, and the
|
131
|
+
second is the Rake task.
|
132
|
+
|
133
|
+
**1. yard Command-line Tool**
|
134
|
+
|
135
|
+
YARD comes packaged with a executable named `yard` which can control the many
|
136
|
+
functions of YARD, including generating documentation, graphs running the
|
137
|
+
YARD server, and so on. To view a list of available YARD commands, type:
|
138
|
+
|
139
|
+
```sh
|
140
|
+
$ yard --help
|
141
|
+
```
|
142
|
+
|
143
|
+
Plugins can also add commands to the `yard` executable to provide extra
|
144
|
+
functionality.
|
145
|
+
|
146
|
+
### Generating Documentation
|
147
|
+
|
148
|
+
<span class="note">The `yardoc` executable is a shortcut for `yard doc`.</span>
|
149
|
+
|
150
|
+
The most common command you will probably use is `yard doc`, or `yardoc`. You
|
151
|
+
can type `yardoc --help` to see the options that YARD provides, but the
|
152
|
+
easiest way to generate docs for your code is to simply type `yardoc` in your
|
153
|
+
project root. This will assume your files are
|
154
|
+
located in the `lib/` directory. If they are located elsewhere, you can specify
|
155
|
+
paths and globs from the commandline via:
|
156
|
+
|
157
|
+
```sh
|
158
|
+
$ yardoc 'lib/**/*.rb' 'app/**/*.rb' ...etc...
|
159
|
+
```
|
160
|
+
|
161
|
+
The tool will generate a `.yardoc` file which will store the cached database
|
162
|
+
of your source code and documentation. If you want to re-generate your docs
|
163
|
+
with another template you can simply use the `--use-cache` (or -c)
|
164
|
+
option to speed up the generation process by skipping source parsing.
|
165
|
+
|
166
|
+
YARD will by default only document code in your public visibility. You can
|
167
|
+
document your protected and private code by adding `--protected` or
|
168
|
+
`--private` to the option switches. In addition, you can add `--no-private`
|
169
|
+
to also ignore any object that has the `@private` meta-tag. This is similar
|
170
|
+
to RDoc's ":nodoc:" behaviour, though the distinction is important. RDoc
|
171
|
+
implies that the object with :nodoc: would not be documented, whereas
|
172
|
+
YARD still recommends documenting private objects for the private API (for
|
173
|
+
maintainer/developer consumption).
|
174
|
+
|
175
|
+
You can also add extra informative files (README, LICENSE) by separating
|
176
|
+
the globs and the filenames with '-'.
|
177
|
+
|
178
|
+
```sh
|
179
|
+
$ yardoc 'app/**/*.rb' - README LICENSE FAQ
|
180
|
+
```
|
181
|
+
|
182
|
+
If no globs precede the '-' argument, the default glob (`lib/**/*.rb`) is
|
183
|
+
used:
|
184
|
+
|
185
|
+
```sh
|
186
|
+
$ yardoc - README LICENSE FAQ
|
187
|
+
```
|
188
|
+
|
189
|
+
Note that the README file can be specified with its own `--readme` switch.
|
190
|
+
|
191
|
+
You can also add a `.yardopts` file to your project directory which lists
|
192
|
+
the switches separated by whitespace (newlines or space) to pass to yardoc
|
193
|
+
whenever it is run. A full overview of the `.yardopts` file can be found in
|
194
|
+
{YARD::CLI::Yardoc}.
|
195
|
+
|
196
|
+
### Queries
|
197
|
+
|
198
|
+
The `yardoc` tool also supports a `--query` argument to only include objects
|
199
|
+
that match a certain data or meta-data query. The query syntax is Ruby, though
|
200
|
+
a few shortcuts are available. For instance, to document only objects that have
|
201
|
+
an "@api" tag with the value "public", all of the following syntaxes would give
|
202
|
+
the same result:
|
203
|
+
|
204
|
+
```sh
|
205
|
+
--query '@api.text == "public"'
|
206
|
+
--query 'object.has_tag?(:api) && object.tag(:api).text == "public"'
|
207
|
+
--query 'has_tag?(:api) && tag(:api).text == "public"'
|
208
|
+
```
|
209
|
+
|
210
|
+
Note that the "@tag" syntax returns the first tag named "tag" on the object.
|
211
|
+
To return the array of all tags named "tag", use "@@tag".
|
212
|
+
|
213
|
+
Multiple `--query` arguments are allowed in the command line parameters. The
|
214
|
+
following two lines both check for the existence of a return and param tag:
|
215
|
+
|
216
|
+
```sh
|
217
|
+
--query '@return' --query '@param'
|
218
|
+
--query '@return && @param'
|
219
|
+
```
|
220
|
+
|
221
|
+
For more information about the query syntax, see the {YARD::Verifier} class.
|
222
|
+
|
223
|
+
**2. Rake Task**
|
224
|
+
|
225
|
+
The second most obvious is to generate docs via a Rake task. You can do this by
|
226
|
+
adding the following to your `Rakefile`:
|
227
|
+
|
228
|
+
```ruby
|
229
|
+
require 'yard'
|
230
|
+
|
231
|
+
YARD::Rake::YardocTask.new do |t|
|
232
|
+
t.files = ['lib/**/*.rb', OTHER_PATHS] # optional
|
233
|
+
t.options = ['--any', '--extra', '--opts'] # optional
|
234
|
+
t.stats_options = ['--list-undoc'] # optional
|
235
|
+
end
|
236
|
+
```
|
237
|
+
|
238
|
+
All the settings: `files`, `options` and `stats_options` are optional. `files` will default to
|
239
|
+
`lib/**/*.rb`, `options` will represents any options you might want
|
240
|
+
to add and `stats_options` will pass extra options to the stats command.
|
241
|
+
Again, a full list of options is available by typing `yardoc --help`
|
242
|
+
in a shell. You can also override the options at the Rake command-line with the
|
243
|
+
OPTS environment variable:
|
244
|
+
|
245
|
+
```sh
|
246
|
+
$ rake yard OPTS='--any --extra --opts'
|
247
|
+
```
|
248
|
+
|
249
|
+
**3. `yri` RI Implementation**
|
250
|
+
|
251
|
+
The yri binary will use the cached .yardoc database to give you quick ri-style
|
252
|
+
access to your documentation. It's way faster than ri but currently does not
|
253
|
+
work with the stdlib or core Ruby libraries, only the active project. Example:
|
254
|
+
|
255
|
+
```sh
|
256
|
+
$ yri YARD::Handlers::Base#register
|
257
|
+
$ yri File.relative_path
|
258
|
+
```
|
259
|
+
|
260
|
+
Note that class methods must not be referred to with the "::" namespace
|
261
|
+
separator. Only modules, classes and constants should use "::".
|
262
|
+
|
263
|
+
You can also do lookups on any installed gems. Just make sure to build the
|
264
|
+
.yardoc databases for installed gems with:
|
265
|
+
|
266
|
+
```sh
|
267
|
+
$ yard gems
|
268
|
+
```
|
269
|
+
|
270
|
+
If you don't have sudo access, it will write these files to your `~/.yard`
|
271
|
+
directory. `yri` will also cache lookups there.
|
272
|
+
|
273
|
+
**4. `yard server` Documentation Server**
|
274
|
+
|
275
|
+
The `yard server` command serves documentation for a local project or all installed
|
276
|
+
RubyGems. To serve documentation for a project you are working on, simply run:
|
277
|
+
|
278
|
+
```sh
|
279
|
+
$ yard server
|
280
|
+
```
|
281
|
+
|
282
|
+
And the project inside the current directory will be parsed (if the source has
|
283
|
+
not yet been scanned by YARD) and served at [http://localhost:8808](http://localhost:8808).
|
284
|
+
|
285
|
+
### Live Reloading
|
286
|
+
|
287
|
+
If you want to serve documentation on a project while you document it so that
|
288
|
+
you can preview the results, simply pass `--reload` (`-r`) to the above command
|
289
|
+
and YARD will reload any changed files on each request. This will allow you to
|
290
|
+
change any documentation in the source and refresh to see the new contents.
|
291
|
+
|
292
|
+
### Serving Gems
|
293
|
+
|
294
|
+
To serve documentation for all installed gems, call:
|
295
|
+
|
296
|
+
```sh
|
297
|
+
$ yard server --gems
|
298
|
+
```
|
299
|
+
|
300
|
+
This will also automatically build documentation for any gems that have not
|
301
|
+
been previously scanned. Note that in this case there will be a slight delay
|
302
|
+
between the first request of a newly parsed gem.
|
303
|
+
|
304
|
+
|
305
|
+
**5. `yard graph` Graphviz Generator**
|
306
|
+
|
307
|
+
You can use `yard graph` to generate dot graphs of your code. This, of course,
|
308
|
+
requires [Graphviz](http://www.graphviz.org) and the `dot` binary. By default
|
309
|
+
this will generate a graph of the classes and modules in the best UML2 notation
|
310
|
+
that Graphviz can support, but without any methods listed. With the `--full`
|
311
|
+
option, methods and attributes will be listed. There is also a `--dependencies`
|
312
|
+
option to show mixin inclusions. You can output to stdout or a file, or pipe directly
|
313
|
+
to `dot`. The same public, protected and private visibility rules apply to `yard graph`.
|
314
|
+
More options can be seen by typing `yard graph --help`, but here is an example:
|
315
|
+
|
316
|
+
```sh
|
317
|
+
$ yard graph --protected --full --dependencies
|
318
|
+
```
|
319
|
+
|
320
|
+
|
321
|
+
## Changelog
|
322
|
+
|
323
|
+
See {file:CHANGELOG.md} for a list of changes.
|
324
|
+
|
325
|
+
## License
|
326
|
+
|
327
|
+
YARD © 2007-2018 by [Loren Segal](mailto:lsegal@soen.ca). YARD is
|
328
|
+
licensed under the MIT license except for some files which come from the
|
329
|
+
RDoc/Ruby distributions. Please see the {file:LICENSE} and {file:LEGAL}
|
330
|
+
documents for more information.
|