|
|
|
|
|
|
by sophiabits
777 days ago
|
|
|
Happens a lot with junction tables ime. e.g. At my last job we had three tables: user, stream, user_stream. user_stream is an N:N junction between a user and a stream A user is free to leave and rejoin a stream, and we want to retain old data. So each user_stream has columns id, user_id, stream_id (+ others) Issues occur when people write code like the following: streamsService.search({
withIds: userStreams.map((stream) => stream.id),
}); The issue is easily noticed if you name the “stream” parameter “userStream” instead, but this particular footgun came up _all_ the time in code review; and it also occurred with other junction tables as well. Branded types on the various id fields completely solve this mistake at design time. |
|
|