You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, when we emit meta data of one property that is defined as:
classA{
@Property()p1: 's1'|'s2';}
We emit the metadata as:
__metadata("design:type",String)
So, whoever is using this metadata cannot know the literal types of p1. A library author has to decorate the literal types s1 and s2 in order to access these literal types:
Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.
Right now, when we emit meta data of one property that is defined as:
We emit the metadata as:
So, whoever is using this metadata cannot know the literal types of
p1
. A library author has to decorate the literal typess1
ands2
in order to access these literal types:Why don't we just emit it as an array instead?
Related to:
#12703
The text was updated successfully, but these errors were encountered: