API compatibility is broken since 0696656 about dscribe HOT 1 CLOSED

Hi @link89!

This is indeed intentional. We wanted to start using consistent naming across all descriptors and this renaming is part of it. While ensuring backwards compatibility would not be a big problem, we wanted to avoid keeping two alternative names around for too long. I believe we have used the best practices in doing so:

• The properties were marked as deprecated in v1.2.2, see changelog here.
• This breaking change in the naming was introduced when we bumped up our major version number from 1.x to 2.x: this indicates backwards incompatible changes.

As a user you have two options:

1. You can fix your dscribe dependency to version 1.x: your old scripts will work with this version.
2. You can choose to update your scripts to conform with 2.x

Hope this helps.

from dscribe.