We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We need a nicer way of renaming special properties that can be defined my multiple keys.
For instance, .created() returns the value of either created or createdAt. This causes inconsistent behaviour.
.created()
created
createdAt
identify.traits({ createdAt: 'created_at' }); // Ignores created completely
var created = identify.created(); // uses either created or createdAt, whichever is available.
The text was updated successfully, but these errors were encountered:
When we address this, we should address the following at the same time:
If you use the method name, that will work to get the value, but with an insidious side effect:
identify.traits({ created: 'created_at' }); // uses either created or createdAt, whichever is available. // but... will leave createdAt there :/
Sorry, something went wrong.
No branches or pull requests
We need a nicer way of renaming special properties that can be defined my multiple keys.
For instance,
.created()
returns the value of eithercreated
orcreatedAt
. This causes inconsistent behaviour.The text was updated successfully, but these errors were encountered: