You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be a good idea to start compiling a list of best practices we support. For example, ATProto and Bluesky write have defs.json whereas we seem to be putting the different defs in the schema file they are referenced in. I don't think there is a right or a wrong, but these types of standards for community-lexicon should live in a doc that can be referenced, which would also help focus PR discussions
Let's use this discussion to hash out standards, starting with the defs.json/in file object definitions. I would say our guidance there is to keep them in file, unless there is a special case
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I think it would be a good idea to start compiling a list of best practices we support. For example, ATProto and Bluesky write have
defs.json
whereas we seem to be putting the different defs in the schema file they are referenced in. I don't think there is a right or a wrong, but these types of standards for community-lexicon should live in a doc that can be referenced, which would also help focus PR discussionsLet's use this discussion to hash out standards, starting with the
defs.json
/in file object definitions. I would say our guidance there is to keep them in file, unless there is a special caseBeta Was this translation helpful? Give feedback.
All reactions