remove 'Number' from public property names about stackframe HOT 7 CLOSED

I'm not quite following. Are you referring to lineNumber and columnNumber? How are the properties creating problems?

I don't think the names were chosen to indicate the type of the variable, but I'm definitely not opposed to changing the names, if they cause a problem.

from stackframe.

@oliversalzburg yes, those two properties are exactly what I was referring to. It's not a problem, as much as it is inconvenient.
It would be easier to use with mozilla's project if the property names would just line and column

from stackframe.

@eriwen What's your take on this?

This would be a breaking change, as dependent projects could be referencing the lineNumber and columnNumber properties.

@capaj Would convenience getters that map line to lineNumber and column to columnNumber also be a valid solution?

from stackframe.

@oliversalzburg getters would solve it for me.
I would also be okay with waiting until the next major version. Whichever you prefer.

from stackframe.

@capaj Just to make sure, I assume your use case isn't covered by stacktrace-gps?

from stackframe.

@oliversalzburg I am actually using it to get the actual line/column of a location where error was thrown. I will probably use it-it does exactly what I need. Once I figure out how to get source maps out of SystemJS

from stackframe.

The property names are intended to be as similar to Gecko and V8 Error stack representations.

A getter would work, but stackframe is intended for use even in browsers that don't support ES5 getters. We could provide that and a polyfill, but that would significantly impact the library size.

We could perhaps add aliases such that line and column retrieve those values if this especially painful for some reason. I understand this makes the code a little more verbose but this is in the interest of consistency and clarity.

from stackframe.