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
{{ message }}
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.
I believe that the ability to remix 1 should behave differently. According to the documentation from the remix 1, :addressables example found on the README the Location being remixed with 1 address does the following:
Creates a class called LocationAddress
Duplicates the properties of Addressable within LocationAddress
Creates a table called location_addresses
Creates Location#location_addresses accessor
However when inspecting the database it appears that multiple addresses can technically be applied to 1 location. I'm proposing the following behavior:
In the location_addresses table there should be a unique constraint placed on location_id
Instead of a Location#location_addresses accessor, it should be a singular Location#location_address or Location#address accessor
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I believe that the ability to remix 1 should behave differently. According to the documentation from the
remix 1, :addressables
example found on the README the Location being remixed with 1 address does the following:However when inspecting the database it appears that multiple addresses can technically be applied to 1 location. I'm proposing the following behavior:
location_id
The text was updated successfully, but these errors were encountered: