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

Object literal {} renders as __type #1179

Closed
1 task done
socsieng opened this issue Jan 16, 2020 · 2 comments
Closed
1 task done

Object literal {} renders as __type #1179

socsieng opened this issue Jan 16, 2020 · 2 comments
Labels
bug Functionality does not match expectation

Comments

@socsieng
Copy link
Contributor

Given the following input:

let test1: object;
let test2: {};
let test3: {
  option1: string,
  option2: number,
};

Expected Behavior

test1: object
test2: {}
test3: { option1: string; option2: number }

Actual Behavior

test1: object
test2: _type
test3: { option1: string; option2: number }

Environment

  • Typedoc version: 0.16.6
  • Node.js version: 8.16.0
  • OS: macOS Catalina
@socsieng socsieng added the bug Functionality does not match expectation label Jan 16, 2020
@Gerrit0
Copy link
Collaborator

Gerrit0 commented Jan 17, 2020

This is a really weird bug. It's first a bug with the converter... {} is being converted as a reference type instead of a object literal, and also a bug with the theme since it looks like I forgot the no-children + no-signatures case...

@Gerrit0
Copy link
Collaborator

Gerrit0 commented Jan 17, 2020

Fixed in typedoc-default-themes v0.7.2 and typedoc v0.16.7

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