A social knowledge tool for researchers built on ATProto
1# 2025.04.18
2
3- consider better abstractions for validating annotation values
4- consider better error handling abstractions and avoid returning null values
5- default values in templates - how to think of this?
6- after an annotation is published to atproto, the repo should be updated with the id of that record
7
8# 2025.04.17
9
10- consider creating annotations from a templated context
11 - this means multiple annotations will be created at the same time, so we should have a use-case for that
12 - CreateAnnotationsFromTemplate - so we can properly handle this all as one request and one transaction
13- consider how we want to decouple the annotation creation from the annotation publishing
14 - should it all happen as one, or dispatch an `AnnotationsCreatedFromTemplate` event and then handle that event which will them interact with at proto and manage all of that logic