Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#1424 closed defect (invalid)

reflection deprecated?

Reported by: [email protected] Owned by: anonymous
Priority: lowest Milestone:
Component: General Version: 0.3
Keywords: Cc:
Blocked By: Blocking:


I'm trying to use the reflective methods that come with dojo.

I see the method I want in dojo.reflect.reflection...which is getProperties and I give it a go.

Well, seems like reflection will not import and I suspect that is because of this:

dojo.deprecated("dojo.reflect", "merged into dojo.lang (dojo.lang[type])", "0.4");

So I look around all over and try to find the method somewhere in the lang module, I look especially in type since that seems to be the package that is hinted at with the lang[type].


So now what?

Is there a deprecation process with respect to this stuff?

I'm probably just going to remove the deprecated lines in the reflect package until the alternative pops up.

I'll be glad to help with documenting a deprecation process, along with examples if there's interest.

Change History (4)

comment:1 Changed 15 years ago by [email protected]

Priority: normallowest


Looks like getting the property names on an object is as simple as for (p in object)

so getProperties was perhaps overkill. If that's the case then it would be great if there was a deprecation note on discontinued methods letting developers know what the preferred way of doing the operation is.

comment:2 Changed 15 years ago by dylan

Milestone: 0.4

comment:3 Changed 15 years ago by Tom Trenka

Resolution: invalid
Status: newclosed

Reflection was marked for removal in 0.4 with the 0.3 release; there was close enough duplication in the rest of lang that having a separate reflection namespace no longer made sense.

comment:4 Changed 15 years ago by (none)

Milestone: 0.4

Milestone 0.4 deleted

Note: See TracTickets for help on using tickets.