AMO:v4/Planning: Difference between revisions

Line 15: Line 15:
* As close to brainless escaping as possible for data in views
* As close to brainless escaping as possible for data in views
** But be mindful of performance - the current escaping does too much
** But be mindful of performance - the current escaping does too much
*** Escaping only when things are actually printed is as good as it gets
* Unit tests that don't run out of memory and can be monitored.  Expanded test data.
* Unit tests that don't run out of memory and can be monitored.  Expanded test data.
** ...and that aren't a hassle to write and don't kill you inside.  To me, that means powerful introspection and mocking so I can look at the running code at any point in the response cycle.
** ...and that aren't a hassle to write and don't kill you inside.  To me, that means powerful introspection and mocking so I can look at the running code at any point in the response cycle.
Line 24: Line 25:
** Not when we forget to use mb_* strings; anyways, I was including unicode more to make sure we think about it
** Not when we forget to use mb_* strings; anyways, I was including unicode more to make sure we think about it
* Easy debugging/development
* Easy debugging/development
** When there's an error, I want a full report of the stack leading up to the error plus the actual line where we have a problem.
* Logging
* Logging
* Message queue / offline work queue
* Message queue / offline work queue
259

edits