Skip to content

Conversation

@satyam-mishra-pce
Copy link
Contributor

@satyam-mishra-pce satyam-mishra-pce commented Nov 12, 2025

This PR addresses the following changes:

  1. In accordance with atproto docs, unions only allow refs that are an object type or can directly be mapped to object types, therefore, I updated the definitions that were not an object.
  2. Added two more defs: smallImage and largeImage to accept only image mime types.

An unimportant change, but its my OCD that led me to restructure the repository and rename the files. [I can undo if you have some other plans]

I also saw that all the schemas' NSIDs started with "org.hypercerts", except the location.json and defs.json that used "app.certified.*". I don't know if this was an error, so, regardless I put both the files underapp/certified/.

Copy link
Contributor

@aspiers aspiers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I like the tidy-up into directory hierarchies a lot! A couple of comments on the namespacing.

{
"lexicon": 1,
"id": "org.hypercerts.claim",
"id": "org.hypercerts.claim.claim",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This double claim doesn't really make sense. On Telegram it looks like we have at least initial consensus on org.hypercerts.impact.* so in this case it would be org.hypercerts.impact.claim.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. I was unsure of what to keep the name (but it was blocking me with some other development), so I just chose this for a quick resolution.
So, shall I replace all the org.hypercerts.claim.* lexicons with org.hypercerts.impact.*? Or is there some discussion still remaining?

@@ -0,0 +1,71 @@
{
"lexicon": 1,
"id": "app.certified.defs",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a good reason to use app.certified here instead of org.hypercerts? I think we should be consistent and just use org.hypercerts.

The location lexicon is more general than even Hypercerts, so it will go in its own namespace, but I need to discuss with @johnx25bd so in the mean time we were just using app.certified.* for the location lexicon only, but not for the others.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't bother to change the NSIDs because I wasn't sure if it was a mistake or it had a real reason behind it. Let's update it, once you have the discussion. I will update the defs lexicons and all their references to use "org.hypercerts".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants