Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warning Encountered an unescaped open brace without an inline tag in comment starting with version 0.23.0 #1966

Closed
doberkofler opened this issue Jun 28, 2022 · 1 comment
Labels
bug Functionality does not match expectation

Comments

@doberkofler
Copy link

doberkofler commented Jun 28, 2022

Search terms

warning Encountered an unescaped open brace without an inline tag in comment

Expected Behavior

the same as in 0.22.18

Actual Behavior

a warning is shown

Steps to reproduce the bug

warning Encountered an unescaped open brace without an inline tag in comment at ./src/framework/UiElement/private/UiElement.ts:288.
warning Unmatched closing brace in comment at ./src/framework/UiElement/private/UiElement.ts:288.

The line 288 is the first line in the following example:

	/**
	 * Register a blur event handler.
	 *
	 * @param {eventCallbackType} handler - Callback function.
	 * @example
	 * element.onChange(element => {console.log(element.getValueString());});
	 */
	public onBlur(handler: eventCallbackType): void { // eslint-disable-line @typescript-eslint/no-unused-vars
		console.warn(this.getError('The "onBlur" method is not available for this element'));
	}

Environment

  • Typedoc version: 0.23.2
  • TypeScript version: 4.7.4
  • Node.js version: 18.4.0
  • OS: maCOS 12.2
@doberkofler doberkofler added the bug Functionality does not match expectation label Jun 28, 2022
@doberkofler doberkofler changed the title warning Encountered an unescaped open brace without an inline tag in comment starting with version 0.23.1 warning Encountered an unescaped open brace without an inline tag in comment starting with version 0.23.0 Jun 28, 2022
@Gerrit0
Copy link
Collaborator

Gerrit0 commented Jun 28, 2022

Hmm, this is unfortunate. The warning is valid, but for compatibility with horrible JSDoc style example tags, it should probably be suppressed when first scanning through @example blocks in case they'll be treated as code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Functionality does not match expectation
Projects
None yet
Development

No branches or pull requests

2 participants