Fix requirements and improve the technical docs#4551
Merged
Conversation
This has been fully tested locally from a fresh client.
MatthiasWiesmann
approved these changes
Oct 30, 2025
pascalfleury
added a commit
to pascalfleury/schemaorg
that referenced
this pull request
Oct 30, 2025
* Fix the requirements so they find all needed modules. This has been fully tested locally from a fresh client. * Improve the docs for working with a local copy of the repository.
MatthiasWiesmann
pushed a commit
that referenced
this pull request
Oct 30, 2025
* Fix the requirements so they find all needed modules. This has been fully tested locally from a fresh client. * Improve the docs for working with a local copy of the repository.
love1120520
reviewed
Dec 27, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The requirement for api==0.0.7 does not resolve with pip3, but it seems to be built-in so no need for it.
Also, give a few more pointers to solve the Ruby issues should there be any.