Mandatory tags...

[aNinjaneer]

Can we pleeeeaaaaaassssssseeeeeeeeeeeeeeee get rid of MANDATORY tags? I understand having them be optional, but sometimes modules get conflicting tags selected in them that you are not actually able to modify, and it breaks the ability for the project to compile. I honestly have never used tags, and don't think I ever will. And even if I did, they should probably be defined in the user space, not the firmware. I would get soooo many hours of my life back if I didn't have to constantly struggle with mandatory tags and tag conflicts...

[Stephen Dean]

Changes to this are being investigated.

[aNinjaneer]

Changes to this are being investigated.

Thank you! Sorry, I was on a rant late last night. I was getting so frustrated that I literally ripped the boost control module out of my package and implemented my own. lol

[Salasko Racing]

Bringing this back up again. These tags honestly take up more time that writing entire features. Somehow they get messed up inside modules and we aren't allowed to modify them. They add zero or negative value (how many people can't find something because "normal" is checked in tune) Could we at least make them optional they literally more than double development time in many cases. Currently been up against the wall for over an hour trying to figure out why I can't get a tag to show up in a indexed switch...

I'm with aNinjaneer I'm about to have to rewrite another module, I've actually already done the boost control as well...

[Salasko Racing]

Apparently I just had to bitch about this because I figured it out. Still hate the tags though.

[MalcolmG]

If this is the voting thread, I'd also be happy to see tags disappear from Build and Tune