3 ms·

You're taking about securing the data itself, which has nothing to do with its parent structure.

• ang_cire 3y ago
  And in the manifesto the author says > I’m not smart enough to figure out how to transform data between different layers of the system, so I just don’t. I use the same represetnation in the UI layer and the storage layer. That has nothing to do with the data structure, is about how the data is being represented in the backend vs the frontend. It's explicitly about changing the data itself. Stuff like url-encoding and escaping characters are examples of transforming data to be represented differently in the backend (where e.g. it's encoded or escaped) from the frontend (where it's displayed in "proper" formatting).
  • nerdchum 3y ago
    Yeah, other than sanitizing and validating, you shouldn't be transforming data or you're headed into a state management bug nightmare.
    • ang_cire 3y ago
      So you think that if e.g. Stack exchange is storing code examples in their database, they shouldn't transform the special characters into e.g. url-encoding or some other escaped format? How are you going to validate it doesn't do something harmful? And also, you keep mentioning sanitization as though it's not inherently a transform. Stripping out whitespace? That's a transform. Just because it's a one-directional transform doesn't make it not one.