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
Feature request: baseline file input with mask #109
Comments
I believe this is super useful, but I would also imagine this requires a decent amount of work because this requires our plugin to understand the gradle script. |
It may already be enough to use what information IntelliJ can provide. For example, the plugin could look for baseline files relative to module/project content root and maybe it's possible to implement some variable substitution so that the mask can include things like, for example, Anyway, basis for this idea is that IntelliJ organises Gradle projects in modules and uses module relative paths for quite a bit of configuration already so it might not actually be necessary to touch Gradle buildscripts for this. It would be less convenient for the user than just taking the configuration directly from Gradle but it could achieve the goal quite decently. Though... From my own experiences with developing IntelliJ plugins, I'm not sure which idea is less work... |
I'd like this feature as well. It's fairly common for me to have multiple Gradle builds in a single IJ project. For example, when developing a library at the same time as some other piece of sw that uses it – that's where Gradle Composite builds come in and IJ has support for that, too, so it's only natural to have such builds in a single IJ project. I'd be fine having to configure it manually on a per-module basis, but an automatically detected setup would be awesome. |
I have an android project with multiple modules and separate baseline files in each module. I want to have the ability to input the baseline file location like a mask at the plugin settings page.
The text was updated successfully, but these errors were encountered: