Rub21 left a comment (openstreetmap/openstreetmap-website#7146)
This PR is ready to review.
For new uploads you can test on the official dev deployment:
https://gpsvisibility.apis.dev.openstreetmap.org/. There you can check that
uploads only offer trackable and identifiable.
What that stack can't cover is the existing-data case, because it builds with a
clean database. So I couldn't reproduce the real situation where a user already
has legacy traces that need updating. For that I seeded my own DB with traces
in all four visibilities (public, private, trackable, identifiable) and ran the
migration on top of it:
https://simplify-gps-visibility.167.233.138.142.nip.io/
On that instance you can check that when you edit an old trace you can move it
to a current value but not back to a legacy one (public/private). It's a
throwaway instance for testing — ping me if you need login credentials.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/7146#issuecomment-4814210430
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/7146/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
