...
Q&A with Feanil Patel (Deactivated) on Inter-service Eventing
What does a good django set of unit tests look like?
Is there a better way to set up test states w/o creating objects in the test itself? (e.g. test case with 0 rows, test cases with 1 row / multiple states, test cases with 2 rows / one state)
What kinds of validations/validation patterns do we use on Django models (if any?) Per Django docs:
Code Block Note that full_clean() will not be called automatically when you call your model’s save() method. You’ll need to call it manually when you want to run one-step model validation for your own manually created models.
-DB validation isn’t always an option & model validations don’t seem to be guaranteed either
Thoughts on sending all Segment events across all repos into one NR table? (Discussed with Robert + Diane earlier today, curious if other people had opinions/thoughts)
Type hinting: Do we want it? Everywhere or just in APIs? etc?