-
Notifications
You must be signed in to change notification settings - Fork 301
upgrade to new pop, go module and bug fixes #188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Overall, looks like great changes! Thank you @k1ng440 ! Can you please give me context on the migration file deletion? With that I think we will be good to go! |
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. |
@bcomnes Please review |
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. |
Hey @bcomnes, my apologies I was not aware of that. I will try gofrs/uuid now |
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
|
I think I reached the same conclusion. Let's go forward with this now, and I'll open an issue to track this tomorrow. |
latest https://github.com/gobuffalo/uuid already delegate all function call to https://github.com/gofrs/uuid gobuffalo/uuid.go
However, Equal function from https://github.com/gofrs/uuid is deprecated in favor of '==' operator (gofrs/uuid#35). gotrue/api/provider/saml.go line 224
I've been successful to build GoTrue (without testing), by changing above function to
|
- Summary
gotrue was using glide and outdated pop orm. it was causing an error on migrations and so on.
- Test plan
I have not added any new feature. therefore all existing passed