[Feature] Better automatic recognition of input signals for playground about ng-doc HOT 4 CLOSED

Thanks very much for such a quick fix! You're right, everything seems to be working now, even the controls (in case I need to use it somewhere).

I have to say that so far I really like ngdoc and it's fantastic how quickly you're responding. Thanks again, if I run into any more problems I'll create another ticket. 🙂

from ng-doc.

In connection to this, I'd like some advice. Since the input signals weren't automatically recognized, I defined the controls manually in NgDocPlaygroundControlConfig.controls, but I failed to create a select control. Even though I used

'size': { type: 'string', options: ['s', 'm', 'l', 'xl'] }

it generated normal text input, not select. I tried several different definitions I could think of, but none succeeded.
Could you please advise me how to write it correctly so that I get a select control with options 's', 'm', 'l' and 'xl'?

from ng-doc.

Amazing research, thank you! I've fixed all the bugs you found, and I've also fixed the issue with the controls field. Now everything should work fine.

About your question:
You should use the name of your type alias as the type if you have it, because specifying the type as string makes NgDoc create a control for managing string type:

'size': { type: 'Size', options: ['s', 'm', 'l', 'xl'] }

Or if for any reason you don't have a separate type, you can also specify the type as NgDocTypeAlias, which is a general type used internally to manage all recognized type alias types that NgDoc can understand (this is not mentioned in the documentation, but I'll add an explanation later):

'size': { type: 'NgDocTypeAlias', options: ['s', 'm', 'l', 'xl'] }

from ng-doc.

🎉 This issue has been resolved in version 17.5.4 🎉

The release is available on:

• v17.5.4
• GitHub release

Your semantic-release bot 📦🚀

from ng-doc.