-
-
Notifications
You must be signed in to change notification settings - Fork 270
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
Add Address model, Factory, Addresses::Country and Addresses::Region #635
Conversation
This looks really nice. FYI, I already have an 'Address' model in my own app, seems like this might conflict with it in a few places. Any way to make it optional? |
Once you pull from the main branch, this line will be merged into your bullet_train/app/models/address.rb Line 4 in 490d472
Same with the bullet_train/app/models/address.rb Lines 1 to 5 in 490d472
|
490d472
to
546e8d8
Compare
6a33cd4
to
0674bdd
Compare
@pascallaliberte, what's the status on this? Is this still something that you'd like to see merged? |
I'll do a check next week on the joint PRs to button things up again and let you know. |
@jagthedrummer it seems it's just the Release tests that don't pass because Otherwise, it's ready to merge. The associated PR bullet-train-co/bullet_train-core#86 is ready to go as well: merge and release js packages. |
@pascallaliberte, yes, I would expect tests to fail in the |
@pascallaliberte, I just pulled this down and played with it and it's super cool! Great work! There's now a merge conflict on the joint PR over in |
Just wanting to capture some stuff that I thought of that we'll want to do soon that relate to these PRs. Most of these are probably best handled in some follow-on PRs.
|
@jagthedrummer I had as a follow-up task to address the super-scaffolding of this type of field. The I think we'll keep the migration in and, as everything in the starter repo, lean on people picking and choosing what they keep from upgrades from upstream, as recommended in the upgrades doc. For docs, I can take it on in a separate PR. The new pattern for self-updating fields is indeed a new approach that deserves a bit of spotlight. But maybe a bit more should be bundled in with this feature before release. Initially it was "let's just ship this", but maybe we're at a point where wrapping a feature like this with docs is required. Up to you. |
@pascallaliberte, I'm totally fine with merging this as is to avoid more merge conflicts, and then following up with the docs. Sound good to you? |
Closes #631
Joint PR:
To Do: