Question

I’m working on a project which makes heavy use of extension methods to convert strings from the UI-layer into their appropriate object-types in the code-layer: (pseudo-code)

// C#

/*
Converts a String from the UI-layer, formatted according to a user-defined
UI-culture preference (in this case from da-DK) into a Double
*/

Double d = "1.000,50".fromWebStringToDouble(); // 1000.5

To unify the programming experience across C# and JavaScript, I want to modify the prototypes of the String, Date and Number object in JavaScript, to implement similar functionality.

Question is: Is this a good idea? We all know that modifying Array‘s prototype seriously cripples the object. But does this horror-scenario apply to the String, Date and Number object?

Answer 1

I really like the way prototype adds methodes to those objects, so, for me, if a Framework is doing that, it’s OK.

Still, it seems more risky to do so in an application :

• when using a Framework, you are expecting people to know how it works
• when developping an application, and adding random methods to Objects, you can’t expect people to know all about those — especially if there is no good documentation about it.

So, in your case, I would only go with that idea if two conditions are met :

• you are doing this in some kind of Framework, that is common to the whole project (and not in a JS file specific to one or two pages)
• there is documentation about methods that are added, what they do, and how to use them.