microsoft / microsoft/reflect-metadata
getMetadataKeys throw TypeError on IE
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.4k
- Forks
- 190
- Avg merge
- 13h 52m
- Merged PRs (30d)
- 1
Description
I am getting following error on calling getMetadataKeys on target object only on IE browser. Code works fine on chrome and firefox -
TypeError
at GetIterator (https://localhost:8787/public/reflect-metadata/reflect-metadata.js:821:13)
at OrdinaryOwnMetadataKeys (https://localhost:8787/public/reflect-metadata/reflect-metadata.js:640:9)
at OrdinaryMetadataKeys (https://localhost:8787/public/reflect-metadata/reflect-metadata.js:603:9)
at OrdinaryMetadataKeys (https://localhost:8787/public/reflect-metadata/reflect-metadata.js:607:9)
at getMetadataKeys (https://localhost:8787/public/reflect-metadata/reflect-metadata.js:417:9)
at validator.recursivelyValidateObject (https://localhost:8787/public/validation/validator.js:34:13)
at validator.validateEntity (https://localhost:8787/public/validation/validator.js:21:13)
at Anonymous function (https://localhost:8787/public/Entity.js:18:17)
at k (https://localhost:8787/public/rsvp/rsvp.min.js:1:2994)
at Y (https://localhost:8787/public/rsvp/rsvp.min.js:1:4671)
We have used property decorator.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the property-decorator case in Internet Explorer and inspect public/reflect-metadata/reflect-metadata.js around GetIterator and OrdinaryOwnMetadataKeys, using the reported stack trace as the entry point. Compare the failing iterator path with the working Chrome and Firefox behavior; done means getMetadataKeys works on the target object in IE without the reported TypeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100