🦋 Changeset detected

Latest commit: 930ddf8

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

Can this wait until 4.13?

Fine for me, @ematipico just said in Discord that moving experimental flags to stable was planned for 4.12, so I tried to submit in time..
But since it already exists under the experimental flag, and is not a new feature, I don't see any issue in 4.13!

The reason to wait is that some people are on vacation that have more context on this feature and would like to get their input on whether it's missing anything or if there's any other reason to delay dropping the flag.

Hey @alexanderniebuhr, talked a bit about this async and we were wondering:

• Is there ever a reason to turn this feature off? Since users have to use the schema manually it's not something that should really be a bother, I don't think. Just a file in the .astro folder that we already own.
  • The only reason I can think to make it configurable would be if there was a performance issue; like if generating the schemas took a while, but I very much doubt it.

If there's not a reason to disable it, we'd probably favor not having the option at all in config and just always doing it.

Since users have to use the schema manually it's not something that should really be a bother, I don't think.

This is the current state, the longterm goal is to improve our language-tools and extension, so users don't need to configure it manually.

Just a file in the .astro folder that we already own.

It's one file for each data collection, so if you have multiple, you get multiple files

The only reason I can think to make it configurable would be if there was a performance issue;

I don't see any performance issue here, but we use a 3rd party dependency to generate schemas, if that fails for any reason, a config flag would allow users to opt-out while we investigate the bug and fix it, otherwise they would need for our fix

we'd probably favor not having the option at all in config and just always doing it.

Your call, I'm happy with both, above is just more context and not any arguments for any sides.

I think everyone is in agreement here in that case, let's remove the config option and just always do this behavior. If there is an error creating the config it can fail gracefully without crashing the dev server.

Glad this is making 4.13, @alexanderniebuhr !

To get you started on the changeset, here are my standard docs on what to write for unflagging an experimental feature!

I can revert them, but I got those automaticity based on the format configuration 🤔