Also what we could live with is some kind of interceptor before setting the field. If we would write xxx.set_importantfield(Obfuscate(data)) there is a chance that developers would have to remember which fields are dealt this way and which aren't
Dňa streda, 18. apríla 2018 9:26:22 UTC+2 Martin Kosicky napísal(-a): > > Hi, is there a native way how to make compiler generate a different > setter/getter in case we have certain options? Some data we would like to > "obfuscate". Sometimes we store serialized protobufs in database and we > don't want to be plain text (some sensitive data), but it's not that > sensitive we just don't want to have it plain text.... > > Is there such a way how to do it natively without hacking the source code > of downloaded code generators? > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
