i get using a long for the type of an id, but i don’t think that should be what’s exposed, since with web apps, and the way the REST server works, we’re leaving our back ends open to some shenanigans. i have started unexposing the ID field (but i have not checked to see if the entities and selections that are passed to the browser are respecting that).
i have also started adding a uuid field, and exposing that, instead.
it might be nice to either be able to make the ID a uuid, or to do what i’m doing: leave it in place, for the relation (but not exposed), and add a UUID.