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

Run dev/build add-on only once #544

Merged
merged 1 commit into from
Jul 24, 2023
Merged

Run dev/build add-on only once #544

merged 1 commit into from
Jul 24, 2023

Conversation

NightJar
Copy link
Contributor

Instead of once for every DataObject that exists in the project. Although there's an early exist after the first execution runs, there are N-1 more runs checking the same thing. This isn't really a change, nor impactful... it is just a touch of code hygiene :)

Because, well, lol
image

Instead of once for every DataObject that exists in the project.
Although there's an early exist after the first execution runs, there
are N-1 more runs checking the same thing. This isn't really a change,
nor impactful... it is just a touch of code hygiene :)
@NightJar NightJar changed the base branch from 5 to 4.0 July 24, 2023 08:40
Copy link
Member

@GuySartorelli GuySartorelli left a comment

Choose a reason for hiding this comment

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

Thank you, that's eminently sensible. I thought this was how it was already to be honest 😅
An additional benefit to this is we're not polluting the DataObject config space with an overly generic enabled property.

@GuySartorelli GuySartorelli changed the base branch from 4.0 to 4.3 July 24, 2023 10:21
@GuySartorelli
Copy link
Member

Failing behat test is unrelated

@GuySartorelli GuySartorelli merged commit 8286b64 into silverstripe:4.3 Jul 24, 2023
@NightJar NightJar deleted the run-only-once-after-build branch July 24, 2023 23:51
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.

2 participants