Can Ecto schema fields be marked private to avoid accidental JSON exposure?
The goal is to prevent sensitive schema fields from being exposed in API responses without relying on per-endpoint allow lists. Ecto.Schema does not define a built-in private or public field option, and field visibility is not enforced at the schema or repository level. Output shaping is typically delegated to JSON serialization, such as Jason derive with on
ecto