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

fix(assets): Fix endpoint not being injected when an integration would enable experimental.assets #7829

Merged
merged 4 commits into from
Jul 27, 2023

Conversation

Princesseuh
Copy link
Member

Changes

What the title says. We'd only check for experimental.assets before running the integration's config setup hooks, so we'd miss it if an integration would enable it for the user (such as Starlight

Testing

Tested manually, we'll be removing this in 3.0 anyway, so

Docs

N/A

@changeset-bot
Copy link

changeset-bot bot commented Jul 26, 2023

🦋 Changeset detected

Latest commit: a68eb72

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions github-actions bot added the pkg: astro Related to the core `astro` package (scope) label Jul 26, 2023
Copy link
Member

@delucis delucis left a comment

Choose a reason for hiding this comment

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

Thanks Erika! LGTM. Plus I trust you.

@@ -89,6 +91,13 @@ class AstroBuilder {
command: 'build',
logging,
});

// HACK: Since we only inject the endpoint if `experimental.assets` is on and it's possible for an integration to
Copy link
Member

Choose a reason for hiding this comment

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

Is it worth a “Remove in 3.0” comment or would we pick it up anyway because experimental.assets will go away so this would be a type error?

Copy link
Member Author

Choose a reason for hiding this comment

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

In 3.0 it's likely that we'll need an option to disable the endpoint (ex: maybe you have your own, maybe you don't want any assets stuff), so we'll still need to check for something in the config still here. So for now I'll leave it like this and update whenever we'll add that option

@Princesseuh Princesseuh merged commit b063a2d into main Jul 27, 2023
@Princesseuh Princesseuh deleted the fix/assets-integration branch July 27, 2023 09:37
@astrobot-houston astrobot-houston mentioned this pull request Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkg: astro Related to the core `astro` package (scope)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants