To avoid compilation errors while loading packages, we have added the support for passing build tags to the DeepSource analyzer. Build tags are an array of strings, and can be added to the .deepsource.toml using the key build_tags in analyzer.meta section.
More details can be found here
Nice work on this @sourya!
I am expecting that if a user misses build_tags during automatic config generation, an SCC Compile Issue would be raised – in this case, how do we communicate to the user that they need to add build_tags to the config?
Perhaps, ask user to fill this during automatic config generation?
I don’t think that asking a user to fill it during config generation would be a good idea, as we want the onboarding step to ask for minimum possible data that can get the user started.
About communicating the user about build tags, we can include information about that in the raised issue.
I don’t think that asking a user to fill it during config generation would be a good idea, as we want the onboarding step to ask for minimum possible data that can get the user started.
Got it, thanks!