Skip to content

Conversation

@Spencer-Smith
Copy link
Contributor

Description

Follow-up to this change, for which I received the feedback that the ML-assisted schema creation workflow should also be accessible. This is not easily done with a single link because these workflows are accessed via buttons on a modal in the Schemas page. I considered two options for doing this:

  1. Add a second link to the ML-assisted workflow. This is what I've done, though I think the text is a little awkward.
  2. Link only to the schemas page and let the user choose the "Create Schema" button on their own.

I'm open to changing strategy here if that's what the people want.

Related Issue

Jira

Motivation and Context

Let's users access the ML-assisted workflow from this page

Screenshots (if appropriate):

Screenshot 2025-11-20 at 2 58 24 PM

I've added the text in parentheses to allow users to use the ML-assisted workflow

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (non-breaking change which does not add functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA or I'm an Adobe employee.
  • I have made any necessary test changes and all tests pass.
  • I have run the Sandbox successfully.
  • I've updated the schema in extension.json or no changes are necessary.
  • My change requires a change to the documentation.

Copy link
Contributor

@carterworks carterworks left a comment

Choose a reason for hiding this comment

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

I like the 2 links.

@Spencer-Smith Spencer-Smith merged commit e09ab59 into main Nov 21, 2025
11 checks passed
@Spencer-Smith Spencer-Smith deleted the fix/addMLSchemaLink branch November 21, 2025 17:02
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.

4 participants