Input difference between workflow_dispatch and workflow_call produces an error "is not defined in object type"

[kudos3939]

Hi,
Below codes produce an actionlint error which I don't expect to get.
The error says that property "second-string" is not defined in object type {first-string: string} but these workflows work fine without fixing "the error".

I think this error should not be appeared in this case.
Is there any way avoiding this?
Or if it is a bug can you fix this?

# example.yml
on:
  workflow_dispatch:
    inputs:
      first-string:
        description: some string
        type: string
  workflow_call:
    inputs:
      first-string:
        description: some string
        type: string
      second-string:
        description: string used only by workflow_call
        type: string
jobs:
  some-job:
    runs-on: ubuntu-latest

    steps:
      - run: echo '${{ inputs.first-string }}'
      - run: echo '${{ inputs.second-string }}'

# example2.yml
on:
  workflow_dispatch:
jobs:
  some-job:
    uses: ./.github/workflows/actionlint-issue-example.yml
    with:
      first-string: "AAA"
      second-string: "BBB"

$ cat .github/workflows/example.yml | docker run --rm -i rhysd/actionlint:latest -color -
<stdin>:21:24: property "second-string" is not defined in object type {first-string: string} [expression]
   |
21 |       - run: echo '${{ inputs.second-string }}'
   |                        ^~~~~~~~~~~~~~~~~~~~

$ docker run --rm rhysd/actionlint:latest -version
1.6.23
installed by building from source
built with go1.19.5 compiler for linux/amd64

[rhysd]

This looks a bug that actionlint does not consider a case where both workflow_dispatch and workflow_call are having an input with the same name. I'll take a look.