Preferences: Disable Feather rule GM2017 (Inconsistent Naming) by default

KormexGit commented 1 year ago

Is your feature request related to a problem?

This particular suggestion is annoying to many existing users and confusing to new users.

ETA: I have seen multiple new users think that the naming suggestions are an actual error that will prevent their game from compiling. I also know many many people who turn feather off entirely due to being annoyed by this particular suggestion, even when told they can turn off this specific one.

Describe the solution you'd like

As said in the title, I think GM2017 should be set to ignore by default, so people who want it can opt-in, but it doesn't cover everyone else's code in squiggly lines. I've seen many many people asking how to turn off this particular suggestion since feather was changed to be enabled by default.

Describe alternatives you've considered

No response

Additional context

No response

Totobal5 commented 1 year ago

yeah please so annoying

Bingdom commented 1 year ago

The option to change naming conventions would be good

Alphish commented 1 year ago

@Bingdom You can already change naming conventions in Preferences, vide this manual page, "Naming Rules" section.

But also I agree that lots of people won't think about Feather-enforcing naming conventions, especially when starting their adventure with gamedev, and also I've found that I can't set up naming rules the way I'd like. Other recommended feature requests:

allowing multiple prefixed for a given type, so I can e.g. prefix my sound assets with bgm_ or sfx_ alongside one another, or use spr_ and bg_ for sprites etc.
Feather-ignoring specific asset groups, so e.g. one can Feather-ignore a local package with different conventions altogether
per-project Feather settings so that different projects can use different rulesets; especially useful when multiple people with different personal Feather settings work on a common project

Hopefully Feather will get some extra love in terms of qualitative features, not just new rules or fixes to existing ones. ^^'

paxer commented 1 year ago

I think it is important to have this option turned on by default. Consistent code style and naming are important parts to make Gamemaker look not only like a tool for beginners but for professional game developers as well. Gamemaker, unlike other engines, is especially suffering in this area. We have lots of tutorials where people use inconsistent code styling all over the place, and this creates an amateur, not professional tool/language kind of experience for those professional developers who are interested in trying Gamemaker for their professional career.

GML itself has consistent naming conversions with all core functions from day one, but it is ignored so often by beginners, and I am really glad that Gamemaker finally introduced Feather and updated all the documentation and tutorials to follow the consistent code styling everywhere.

gojirra55 commented 7 months ago

Scaring the shit out of noobies with arbitrary coding style rules is absolutely whack af GM.

RainyRainbows commented 7 months ago

GRAAAAAH!

KormexGit commented 7 months ago

While browsing the manual, I discovered that the docs think that GM2017 is already disabled by default, even though it isn't

thennothinghappened commented 6 months ago

This has come up again with someone posting about not knowing how to turn this off (though think of all the people who don't post and just give up on it). In the long term, Feather needs a proper explanation and major improvements to its configuration by "massive list of rules and dropdowns in a scrolling list", but in the short term Feather needs to be setup in a way that will give the most value to people without needing to be customised.

The ability to have a naming rule option is great, but when it is on by default and having Feather on bombards people who are totally unfamiliar with it with a heap of warnings about something that's really just a nitpick for their naming choice, that's terrible UX. This should just be one flick of a switch to set this off by default. There's a lot of people who've lost out on Feather's capabilities because their first experience with it was a cascade of useless messages about how Feather doesn't agree with their case choice. Not knowing how to turn this off - even if it is actually pretty simple to do - people then just assume Feather's here just to judge their style choices, turn Feather off completely, and move on without it.

YoYoGames / GameMaker-Bugs