Fix breaking JSDoc changes (#1012)

[mitchell-merry]

Changes

Fixes #1012

• Parameters correctly generate next to the intended parameter (this was a typo I believe)
• Operation comments now generate above the operation instead of inside (in this case there was also a duplicate comment generated when the operation had no operationId)

The example linked in the issue now generates as:

export type operations = {

  /** getVisits description (now attached to getVisits) */
  getVisits: {
    parameters: {
      path: {
        /** @description storeId description (now correctly on the property) */
        storeId: string;
        /** @description storeName description */
        storeName: string;
      };
    };
    responses: {
      /** @description Success */
      200: {
        content: {
          "application/json": components["schemas"]["SchedulerVisitReadModel"];
        };
      };
    };
  };
};

How to Review

The tests were wrong in this instance, so they have been updated as well.

Checklist

• Unit tests updated
• examples/ directory updated (if applicable)

[mitchell-merry]

Need to make a couple changes

[mitchell-merry]

Hi @drwpow, just wondering what's blocking you from merging some of these PRs? I'd like to work on additional features (i.e. #941 ) but I'm hesitant since it seems like this project has stagnated.

[drwpow]

This is a great fix, and great tests. Thank you! Will merge as soon as the lint errors & minor conflicts are resolved.

[drwpow]

Hi @drwpow, just wondering what's blocking you from merging some of these PRs?

I contribute as much time to the project as I can, which is several hours every month. I’d love help with additional maintainers if you’re interested or know someone who is.

[mitchell-merry]

This is a great fix, and great tests. Thank you! Will merge as soon as the lint errors & minor conflicts are resolved.

Thanks! Could you rerun the workflow? I'm getting Response is not a constructor errors on my local (for load.test.ts) for both my branch and main, so I want to make sure that it works in CI (no idea what my issue is on local).

I contribute as much time to the project as I can, which is several hours every month. I’d love help with additional maintainers if you’re interested or know someone who is.

That's good to hear. I want to start using this package, so I'm hoping that it's still being at least somewhat maintained. As long as I can submit PRs and there's someone around to check them, that's good by me :D thanks for what you do.

Edit: Seems good, just needs a merge! @drwpow

[drwpow]

@all-contributors please add @mitchell-merry for code, test, bug

[allcontributors]

@drwpow

I've put up a pull request to add @mitchell-merry! 🎉