Skip to content

Conversation

@andrewelamb
Copy link
Contributor

@andrewelamb andrewelamb commented Oct 23, 2025

Problem:

The new JSONSchema classes need documentation.
The old JSONSchema classes need to be deprecated.
While writing the tutorial a bug was found: JSONSchema.store-async was overwriting its id attribute with the id field from the CreateSchemaResponse . These are not the same thing. JSONSchema.id is an integer identifier created by synapse in string form (ie. 1880). The id from CreateSchemaResponse is a url.

Solution:

Documentation files added for new JSONSchema classes.

Old JSONSchema classes are deprecated. For these, I just deprecated the classes. The old file states This is a beta implementation and is subject to change. Use at your own risk. so i didn't include examples of how to use the new classes here. I can add these if needed.

Tutorials added in this PR

The bug was fixed in JSONSchema.store-async by not updating the id attribute.

@andrewelamb andrewelamb requested a review from a team as a code owner October 23, 2025 17:22
@andrewelamb andrewelamb marked this pull request as draft October 23, 2025 17:22
@andrewelamb andrewelamb marked this pull request as ready for review October 23, 2025 18:57
@jaymedina
Copy link
Contributor

There are broken reference links in the appendix:
image

* You have a working [installation](../installation.md) of the Synapse Python Client.
* Make sure that you have completed the [Project](./project.md) tutorial, which covers creating and managing projects in Synapse. This is a prerequisite because you need a project to organize and store the folder used in this tutorial.
* You are familiar with Synapse concepts: [Project](./project.md), [Folder](./folder.md), [File](./file.md).
* You are familiar with [adding annotations](./annotation.md) to synapse entity.
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: Would also add that familiarity with SchemaOrganization is also necessary

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