Strange Timeline log warning

[mathias]

Just saw this in the logs:

isc_SchedTimeline_0:Calendar.laneNameField must be set to a text-based field since its values may be used as identifiers. The specified field 'userId' is of type 'integer'.

The lanes are all users, so that i can show schedule item on the row for the user it belongs to. It makes sense to use the "userId" field since that's the foreign key in the schedule datasource that is relevant for the row. It has worked fine for as long as i can remember, and i don't remember seeing this log.

IMO it makes more sense to use an integer for an index than a String. What am i missing?

[Isomorphic]

You didn't mention your version - but it looks like this log was added to 13.0 in October 2023 and is present in later versions. The warning was a response to this thread - it reported a bug with using an integer laneNameField, while Lane.name is documented as a String - even when stringified, numeric strings are not considered strictly valid identifiers in JS.

For the moment, it's just a warning - it doesn't enforce anything.