microsoft / microsoft/reflect-metadata
Types Not Reflecting
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.4k
- Forks
- 190
- Avg merge
- 13h 52m
- Merged PRs (30d)
- 1
Description
Using 2 different JSON Serialization libraries I am having an issue regarding type order with Angular 4:
The 2 cases are documented here:
https://github.com/shakilsiraj/json-object-mapper/issues/9
https://github.com/jf3096/json-typescript-mapper/issues/19
The main issue seems to be the types must be defined in a particular order in order to be recognized. Is this ok behavior or is this a bug of the library. As I use the same object multiple places and sometimes have them nested (the app I am working on needs it) What would be the proper way of including them.
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 two type-ordering cases linked in the issue and compare them with the reflect-metadata behavior used by the Angular 4 application. Determine whether declaration order is expected or a library defect; done means documenting the proper usage or identifying a concrete change needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100