Feature Request Type

• Core functionality
• Alteration (enhancement/optimization) of existing feature(s)
• New behavior

Description

The latest version of strawberry supports federation v2.7 and hardcodes the directive urls as such: #3420

The apollo federation version at my company is v2.5 so I've updated our schema generator to manually replace v2.7 with v2.5

It would be nice to be able to set this at the schema level, e.g.
federation.Schema(query=Query, federation_version="v2.5")

At first glance it seems relatively straightforward:

1. Add federation_version argument to the schema, default to "v2.7" if enable_federation_2=True
2. Set enable_federation_2=True if federation_version >= 2
3. Update schema urls with the version so the schema generator writes that version

But I imagine that the versioning actually changes underlying support, so then there are outstanding questions:

• Would we support old federation versions and new ones?
• Would we have to validate the version number against what features are supported?
• Would we just trust the user that they know which features are available if they're setting the version explicity?
• Would it be preferable to overwrite the print_schema function with version instead?

Not sure what the approach should be, but I don't think this library should dictate the federation version, and more explicitly, I think that users of this library should be able to get library updates unrelated to federation version, rather than having to pin to the version before some federation version was explicitly supported / mandated.