Suggestion: reflection for interface?

Interface is a useful tool in TypeScript, but sometimes we'll need to write two pieces of almost identical code for intellisense and functionality respectively.

Is it acceptable to add a simple statement for generating part of interface information (properties)?

E.g.

class SomeClass { }

interface ISubFace {
    abc: string;
    def: number;
}

interface IFace {
    str: string;
    num: number;
    obj: SomeClass;
    sub: ISubFace;
}

var faceInfo = reflect IFace;

Would emit:

var SomeClass = (function () {
    function SomeClass() {
    }
    return SomeClass;
})();

var _ISubFaceReflection = {
    abc: 'string',
    def: 'number'
};
var _IFaceReflection = {
    str: 'string',
    num: 'number',
    obj: SomeClass,
    sub: _ISubFaceReflection
};

var faceInfo = _IFaceReflection;

This will help my ObjectExtensions.ensure library a lot.

Kagami Sascha Rosylight (@saschanaz)

Kagami Sascha Rosylight (@saschanaz) oops. sorry I din't read the comment carefully.

vilic No, I didn't suggest anything but just said that I like your suggestion.

var face: IFace;
ObjectExtensions.ensure(face, reflect IFace);

This will be much better than:

var face: IFace;
ObjectExtensions.ensure(face, { str: "string", num: "number", obj: SomeClass, sub: { abc: "string", def: "number" } });

Kagami Sascha Rosylight (@saschanaz)

Kagami Sascha Rosylight (@saschanaz) yeah, later I found that I misunderstood what you said... T-T my head is full of coffee, and it's too heavy to think...

vilic Haha, me too. It's 1:44 AM here and I feel I have to sleep now. Well... Merry Christmas (or merry Christmas eve) 😄

Kagami Sascha Rosylight (@saschanaz)

Kagami Sascha Rosylight (@saschanaz) lol, Merry Christmas, and good night~ :D

Run time type information (ie reflection) is currently outside our design goals (https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals). If we were to do something like what you're requesting it would most likely surface in the form of attributes like #1557

Hmm, I thought it was easy because it seemed like we only need to do some sort of traversing... But I still look forward to it, annotations are annoying and it's not how JSers code. Any way we just need the certain reflection generated when reflect is there, and it should be somewhat compile-time...

We don't need:

var obj: any;
var reflected = reflect obj;

but we do need:

interface A { /* ... */ }
var reflected = reflect A;

and this should be able to be done on compile-time.

+1 for this feature. It will be of great help to deal with POJO ajax data and convert their types.

Take a look at this project: https://github.com/artifacthealth/tsreflect-compiler.

Meir Gottlieb (@meirgottlieb)

Meir Gottlieb (@meirgottlieb) that is great but I guess it won't fit the needs. :'(

👍 I also think that it would be great to be able to access interfaces via reflection. Though I don't need that level of detail. The name of the interfaces would be enough.

#3148

+1, would be very useful for stubbing interfaces, a-la Mockito (http://mockito.org/), something like:

interface Animal {
   makeSound(): void;
}

const anAnimal = Mock.<Animal>create();
...
anAnimal.makeSound();

Unfortunately tscompiler-reflect project is discontinued. Is there any way to get runtime type check in TypeScript? RTTC was one of the main design goals of AtScript.

+1. I really hope to see typescript supports Java like reflection which is very useful for metadata driven designs such as use type information to generate auto-completion UI. The type information is valuable information which shouldn't be erased at runtime.

+1. This is a must have feature in any grown up language. One cannot be expected to rewrite all the types of an interface over again just to check the type.

The "keyof" and "reflect" is not the same! This has type information and can probably be usefull e.g in Angular2 Dependency Injection, injecting Interfaces.
We can have both or at least "reflect" that is more generic with.

Navigation Menu

Repository navigation

Suggestion: reflection for interface? #1549

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Suggestion: reflection for interface? #1549

Description

Activity

saschanaz commented on Dec 24, 2014

vilicvane commented on Dec 24, 2014

saschanaz commented on Dec 24, 2014

vilicvane commented on Dec 24, 2014

saschanaz commented on Dec 24, 2014

vilicvane commented on Dec 24, 2014

danquirk commented on Jan 6, 2015

vilicvane commented on Jan 6, 2015

saschanaz commented on Jan 6, 2015

ipy commented on Feb 1, 2015

meirgottlieb commented on Feb 3, 2015

vilicvane commented on Feb 4, 2015

remojansen commented on May 14, 2015

electricmonk commented on Dec 2, 2015

typeofweb commented on Feb 29, 2016

jianwu commented on Mar 31, 2016

blue112 commented on Jul 21, 2016

shumy commented on Feb 1, 2017

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions