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

Declare the inputs of GenerateAntoraPlaybook more precisely #40572

Open
wilkinsona opened this issue Apr 29, 2024 · 0 comments
Open

Declare the inputs of GenerateAntoraPlaybook more precisely #40572

wilkinsona opened this issue Apr 29, 2024 · 0 comments
Assignees
Labels
type: task A general task
Milestone

Comments

@wilkinsona
Copy link
Member

Many of the task's inputs are currently captured in a Map<String, Object>. When comparing build scans this makes it hard to determine why the task was or was not up-to-date. data is represented as a Value property. When the value differs, all that we're shown is that "Input 'data' is in both builds but values are different". Splitting this input up into several more finely grained inputs will make build scans more useful.

@wilkinsona wilkinsona added the type: task A general task label Apr 29, 2024
@wilkinsona wilkinsona added this to the 3.3.x milestone Apr 29, 2024
@scottfrederick scottfrederick self-assigned this May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants