Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Introduce beta sitepackage tutorial builder #464

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

linawolf
Copy link
Contributor

  • Add Class constraints to only use allowed builder-version combinations
  • Remove unsupported versions as a drive-by

throw new UnexpectedValueException($constraint, ValidBasePackageVersion::class);
}

if ($value->getBasePackage() === 'site_package_tutorial' && $value->getTypo3Version() !== 13.4) {
Copy link
Member

@benjaminkott benjaminkott Nov 21, 2024

Choose a reason for hiding this comment

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

i think we need to check here for versions available in the packages directory and have it generally available as a validator. this one currently only checks for site_package_tutorial and has a fixed version constraint. this would be handy if we provide more variants of for sitepackages.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is a first POV which could be enhanced to be more soffisticated down the line...

Copy link
Member

Choose a reason for hiding this comment

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

will check the validator does not work with the api endpoint currently - will also check how to add general support.

Payload:

{
  "base_package": "site_package_tutorial",
  "typo3_version": 12.4,
  "vendor_name": "string",
  "vendor_name_alternative": "string",
  "title": "My Sitepackage",
  "description": "Project Configuration for Client",
  "package_name": "string",
  "package_name_alternative": "string",
  "extension_key": "string",
  "repository_url": "https://github.com/FriendsOfTYPO3/introduction",
  "author": {
    "name": "J. Doe",
    "email": "[email protected]",
    "company": "TYPO3",
    "homepage": "https://typo3.com"
  }
}

Copy link
Contributor Author

@linawolf linawolf Nov 22, 2024

Choose a reason for hiding this comment

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

The api end point does not seem to validate whatoever so this seems to be a different issue:

curl -X 'POST' \
  'https://get.typo3.org/api/v1/sitepackage/' \
  -H 'accept: application/zip' \
  -H 'Content-Type: application/json' \
  -d '{
  "base_package": "apfelbaum",
  "typo3_version": 8.7,
  "vendor_name": "string",
  "vendor_name_alternative": "string",
  "title": "My Sitepackage",
  "description": "Project Configuration for Client",
  "package_name": "string",
  "package_name_alternative": "string",
  "extension_key": "string",
  "repository_url": "https://github.com/FriendsOfTYPO3/introduction",
  "author": {
    "name": "J. Doe",
    "email": "[email protected]",
    "company": "TYPO3",
    "homepage": "https://typo3.com"
  }
}'

just gives you a 500 currently

@benjaminkott benjaminkott force-pushed the task/sitepackage_tutorial branch 2 times, most recently from b16bca2 to ae30c62 Compare November 22, 2024 10:40
Copy link
Member

@benjaminkott benjaminkott left a comment

Choose a reason for hiding this comment

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

validator is not working when using the API endpoint

@linawolf
Copy link
Contributor Author

Ill have a look

- Add Class constraints to only use allowed builder-version combinations
- Remove unsupported versions as a drive-by
@benjaminkott
Copy link
Member

will finish #466 first and rebase this one on top

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.

2 participants