Skip to content
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

2.7 New Field Type: Address / Map #3623

Conversation

JoryHogeveen
Copy link
Member

@JoryHogeveen JoryHogeveen added Type: Feature Features that add entirely new functionality that was not there before Patch Status: In Progress Issue or PR is currently in progress but not yet done labels Jul 3, 2016
@JoryHogeveen JoryHogeveen added this to the Pods 2.7 milestone Jul 3, 2016
@JoryHogeveen JoryHogeveen self-assigned this Jul 3, 2016
@JoryHogeveen JoryHogeveen changed the title New Field Type: Address / Map 2.7 New Field Type: Address / Map Jul 3, 2016
@JoryHogeveen
Copy link
Member Author

@sc0ttkclark @pglewis
Why not set the regular address fields as default (no map options etc) and add the map options with a component.
This way the address field is a regular field with multiple inputs and a component can extend this field with extra options for Google Maps or even order map providers.

The default address field would be quite similar to the GF address field this way (just regular fields and select boxes)
Let me know your thoughts on this.

@sc0ttkclark sc0ttkclark closed this Jul 6, 2016
@sc0ttkclark sc0ttkclark removed the Status: In Progress Issue or PR is currently in progress but not yet done label Jul 6, 2016
@sc0ttkclark sc0ttkclark mentioned this pull request Jul 6, 2016
56 tasks
@sc0ttkclark sc0ttkclark added Invalid and removed Type: Feature Features that add entirely new functionality that was not there before Patch labels Jul 6, 2016
@sc0ttkclark sc0ttkclark modified the milestones: Pods 2.8, Pods 2.7 Jul 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants