<!-- NOTE 1: It would help if you can first scan the issue tracker before submitting a new issue: https://github.com/gajus/eslint-plugin-jsdoc/issues NOTE 2: If you are running ESLint/`eslint-plugin-jsdoc` from within an IDE, before filing an issue, please be sure to restart the IDE after making any updates to ensure you are indeed getting errors with the updated version. Running `eslint` on the command line may also be helpful in allowing you to better provide us with the error details including the stack trace. NOTE 3: If you have a bug specifically related to the parsing of types, e.g., the `some-unrecognized+type-syntax` (within curly brackets) in: /** * @param {some-unrecognized+type-syntax} myName */ ...then please file instead at https://github.com/simonseyock/jsdoc-type-pratt-parser/issues/ --> <!-- TIP: If you have a complicated config with `overrides`, you can simplify the config you provide us by running `eslint` with `--print-config` and the file that is triggering the error. See: https://eslint.org/docs/user-guide/command-line-interface#print-config --> ## Expected behavior <!-- Provide a detailed description of how you expected the software to --> <!-- behave. --> I expected this to be allowed: ```js /** @param {string} text */ const a = x => x; ``` When not using star prefix, the proper alignment means that the start and end of the comment don't have any indentation. For example, this should be caught: ```js /** @param {string} text */ const a = x => x; ``` ## Actual behavior It complains. ## ESLint Config <!-- What is the minimal config that reproduces the issue? Please try to reproduce with only a single rule in your config (along with the minimal number of options or settings that are needed to trigger the error). --> ```js { 'jsdoc/check-alignment': 'error' } ``` ## ESLint sample Already shared. ## Environment - Node version: 22.12.0 - ESLint version 9.18 - `eslint-plugin-jsdoc` version: 50.6.2