YARD `@overload` not taken into account about inch

[rrrene]

Hi there,

I'm not sure I ever got back to you about this. It should be fixed by now (0.4 release to be precise).

I will close this ticket, but if it wasn't fixed just call me out on it! Thanks for your bug report!

[denisdefreyne]

Works like a charm, thanks! (Nice and green now)

[yasuhito]

Hi, this issue seems still exists with inch 0.4.2.

Code:

    # Creates a Hello OpenFlow message.
    #
    # @overload initialize()
    #   @example
    #     Hello.new
    #
    # @overload initialize(transaction_id)
    #   @example
    #     Hello.new(123)
    #   @param [Number] transaction_id
    #     An unsigned 32-bit integer number associated with this
    #     message. If not specified, an auto-generated value is set.
    #
    # @overload initialize(user_options)
    #   @example
    #     Hello.new(transaction_id: 123)
    #     Hello.new(xid: 123)
    #   @param [Hash] user_options the options to create a message with.
    #   @option user_options [Number] :transaction_id
    #   @option user_options [Number] :xid an alias to transaction_id.
    def initialize(user_options = {})
        #...

has this output:

$ inch show "Pio::Hello#initialize"
# Pio::Hello#initialize                                                                                                                                                           
┃ -> /Users/yasuhito/play/pio/lib/pio/hello.rb:45
┃ ----------------------------------------------------------------
┃ Grade: A - Seems really good 
┃ ----------------------------------------------------------------
┃ + Add a code example (optional)
┃ + Describe the parameter 'user_options'
┃ + Describe the parameter 'transaction_id'
┃ ----------------------------------------------------------------

The comments are correctly graded as A but suggestions does not disappear.

[rrrene]

Ah, so we are kind-of half-way there 😄

Ok, I will have a look!

[rrrene]

@yasuhito I just released Inch 0.4.3, which fixes the problem described above.

Thanks again for your detailed bug report! 👍