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

corner case fixed: task should run again after test file was modified #1

Open
wants to merge 37 commits into
base: master
Choose a base branch
from

Conversation

alexvas
Copy link

@alexvas alexvas commented Sep 24, 2018

I've found your presentation at Droidconf and was deeply impressed by TTD approach you undertook. This is a way that any new gradle plugin should be created. So I chose your project as a base for my kotlin2typescript gradle plugin.

Meanwhile, I think I've found a corner case for the current LOC plugin. Assert that task should run again after test file was modified if failing for now. I'd like to provide refactored plugin that fixes the issue. I did that just for fun and hope you'll have it too reviewing my pull request.

see GradleRunner.withDebug(boolean flag)
instead of hardcoded string
this one:
As part of making the publishing plugins stable, the 'deferred
configurable' behavior of the 'publishing {}' block has been deprecated.
In Gradle 5.0 the 'enableFeaturePreview('STABLE_PUBLISHING')' flag will
be removed and the new behavior will become the default. Please add
'enableFeaturePreview('STABLE_PUBLISHING')' to your settings file and do
 test run by publishing to a local repository. If all artifacts are
 published as expected, there is nothing else to do. If the published
 artifacts change unexpectedly, please see the migration guide for more
 details:
 https://docs.gradle.org/4.10.2/userguide/publishing_maven.html#publishing_maven:deferred_configuration.
`task should run again after test file was modified`
also remove intermediate input task so dump input file summary to FS
is now avoided
guru.stefma.gloc -> kotlin2ts
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.

1 participant