analytics.identify sends traits through context when userId is null (version 1.53.0)

[seg-leonelsanches]

On version 1.53.0, I tested with a client the following call:

analytics.identify(null, {
   prop1: 1,
   prop2: "2"
});

The properties will go to context payload in Segment, instead of traits.

The problem doesn't happen in version 1.52.0. I advised the client to downgrade the library.

[silesky]

@seg-leonelsanches thank you for your report.
I see that you get both context and traits.

I can reproduce this odd behavior when passing null as the first argument to identify. This differs from the classic behavior, so I can safely label this as a bug.

I do not see any difference in the behavior between 1.53.x and 1.52.x -- (I tested with an versions that > 1 year old and it had the same bug), so it's strange to me that you're saying that the problem doesn't happen in 1.52.0

As a "workaround", instead of using null, you can use undefined:
e.g.

analytics.identify(undefined, {
   prop1: 1,
   prop2: "2"
});

[seg-leonelsanches]

Hi @silesky. We got to reproduce also in 1.52.0. The customer is not using userId, but another column called CPF (it's like the SSN for Brazil):