refactor RDoc markup handling for improved loading and initialization#1608
refactor RDoc markup handling for improved loading and initialization#1608seuros wants to merge 2 commits intolsegal:mainfrom
Conversation
|
This seems to fail all tests. Can you look into this? |
|
Oh cool, i see you dropped legacy support for 2.6. Do you think we should go at a safer zone to support only 3.2+ since anything before is EOL. I have some yard plugins that work only in those version as they use edge gem or ruby features. |
|
(oops earlier comment was incorrect) We would need to support ruby 2.x+ even if we can't run CI tests against them. CI doesn't represent what versions of ruby yard supports. |
|
Remember that dropping support doesn't mean that version 2.x cannot install yard suddenly. It just means that future versions won't be installable. Those legacy versions don't even install in recent hardware like Apple Silicon, and lot it dependencies are EOL or have huge security problem (eg: openssl 3 compatibility). |
|
Marking this as closed. Upon further review this is not a needed change in YARD; it seems to drop support for older RDoc versions for no reason even though they continue to work in YARD. YARD does not drop support just because libraries are old. rdoc < 6 is still installable on plenty of machines, including in Ruby 4.x: |
Description
rdoc class had support for a rdoc version that is 12 years old.
added https for the homepage.
Completed Tasks
bundle exec rakelocally (if code is attached to PR).