search

leandroBorgesFerreira / dag-command

Affected gradle modules by branch
Apache License 2.0
46 stars 11 forks source link

lifting root of repo design constraint #28

Closed softprops closed 8 months ago

softprops commented 1 year ago

from this project's readme

This module assumes that the modules are in the folders in the root of the project

I'd like to use your plugin but within my git repo my gradle build exists under {repo-root}/modules/ which I believe is breaking the assumptions of this plugin. would it be possible to add a configuration property to make this assumption a flexible one? something like 

  dagCommand {
    filter = "all"
    defaultBranch = "origin/main"
    outputType = "json"
    printModulesInfo = true
    projectPrefix = "modules/" // <- strips this off in git diff calculation
  }
leandroBorgesFerreira commented 1 year ago

Hello @softprops. Sorry for the late reply, I didn't see your issue =|.

Your request makes perfect sense. More than this... the limitation of where the modules should exist should be improved. I need to find a way to support modules in any place of the project.

I'll do some research and update this issue.

leandroBorgesFerreira commented 8 months ago

It has been a while, but this is fixed in the version 1.10.0. Now you can choose any module that you prefer.