Repository navigation
Conversation
461ec5a to
84fa999
Compare
e7f7eb0 to
0c0b65a
Compare
|
@Lee-W Can you update the screenshot on how they look with recent changes |
0c0b65a to
7d9cbd0
Compare
|
The screenshots are still pretty much the same. but i just took new ones |
|
I am not fully sure on the UX -- since Toolsets is a concept only for Common AI provider.. can you think of a more generalized solution |
Lee-W
changed the title
|
What about making them |
Yeah I like that, want to give that a shot to see how it looks |
|
updated the screenshot in the description |
7ca9c10 to
aaaf5c4
Compare
Toolsets became a registry module category without any record of what they connect to, so a visitor could see that a provider ships nine toolsets but not that one of them reaches every Airflow connection and another reads Apache Iceberg tables. Reading the same provider.yaml field the documentation page reads keeps the two from telling different stories about the same release.
Toolsets are a common.ai concept, so the provider page now shows one External services card that lists every connection type and toolset module declaring external services, each row labelled with its source type. The per-connection external services table moves out of the Connections card into this card instead of being shown twice.
The provider.yaml schema does not allow `external-services` on a toolset, so `toolset_services` was empty for every provider. - Remove `toolset_services` from the extractors, the contract models, and the version page template - Show connection types only, so the "Source type" column is dropped
aaaf5c4 to
4ee4621
Compare
This branch has not been deployed
2 participants
A visitor could see the connection types a provider ships, but not which external services each one reaches. The provider page now has one External Services card listing every connection type that declares external services. The per-connection table moves out of the Connections card into it, so the same information isn't shown twice. Reading the same provider.yaml fields the documentation page reads keeps the two from telling different stories about the same release.
common ai
amazon (without toolset)
snowflake (with toolset ,but no common ai)
Was generative AI tooling used to co-author this PR?
Generated-by: [Claude] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.