You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now both tests and source targets are generated as ts_projects. This is fine in principle as a default, but disallows me to generate a different kind of target for my tests since both have the same kind so gazelle's map_kind directive applies to both tests and source targets.
Describe the feature
Tests target should have a different kind (in gazelle terms) than source targets. If this were the case, I could independently configure the kind of my source files to be my own fe_library rule and have my tests be my own my_special_test rule.
The text was updated successfully, but these errors were encountered:
What is the current behavior?
Right now both tests and source targets are generated as
ts_project
s. This is fine in principle as a default, but disallows me to generate a different kind of target for my tests since both have the samekind
so gazelle'smap_kind
directive applies to both tests and source targets.Describe the feature
Tests target should have a different
kind
(in gazelle terms) than source targets. If this were the case, I could independently configure the kind of my source files to be my ownfe_library
rule and have my tests be my ownmy_special_test
rule.The text was updated successfully, but these errors were encountered: