You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I occasionally use byte and short as the backing type for an Id in SQL Server because int is just too large for my needs. It would be nice to have support for byte and short along side int and long for such scenarios.
Unless I'm missing something, as far as I can tell, I can't make a strongly typed id for those Ids with the current implementation of the library. I'll probably duplicate what the source generator is outputting manually so I can still get a strongly typed id, but it would be nice to have the library take care of those as well.
The text was updated successfully, but these errors were encountered:
Sorry for the lack of attention on this, I got a bit burnt out over the requests with this library 😬 The good news is that for feature requests like this, I think I've found an answer in the big redesign of the library in this PR:
The main idea is to make the library much more maintainable while also giving people a mechanism to customise the generated IDs as much as they like. This will make it easy to make changes or additions like this 🙂
I occasionally use
byte
andshort
as the backing type for an Id in SQL Server becauseint
is just too large for my needs. It would be nice to have support forbyte
andshort
along sideint
andlong
for such scenarios.Unless I'm missing something, as far as I can tell, I can't make a strongly typed id for those Ids with the current implementation of the library. I'll probably duplicate what the source generator is outputting manually so I can still get a strongly typed id, but it would be nice to have the library take care of those as well.
The text was updated successfully, but these errors were encountered: