Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
upgrade to new pop, go module and bug fixes #188
referenced this pull request
Oct 16, 2018
I just tested migration and the file seems to be not required at all. it was probably created before the migrations was added. however i will add it back.
Apologies @k1ng440 I wasn't active on the project during the switch from gorm to pop, so still playing catchup here.
I noticed https://github.com/gobuffalo/uuid is marked depreciated and suggests https://github.com/gofrs/uuid instead. Are you familiar with this situation? If possible, it seems preferable to go with that over a depreciated fork. I'm going to test that out, but if you know anything let me know. I don't necessarily want to block landing this if switching over to that will be a lot of extra work, or not work for some reason. Any insight is appreciated.
well it's not possible to use gofrs/uuid because gobuffalo/pop is using gobuffalo/uuid
if you search uuid in pop, you will see they have used it every where
gotrue/api/provider/saml.go line 224
I've been successful to build GoTrue (without testing), by changing above function to