Add `--ignore-init-modules` to configurable options

[stdedos]

Description

I'd like that autoimport can figure out its opts, akin to pytests addopts

With that, some more documentation examples would be welcome

Possible Solution

Additional context

PS: I am aware of the maintenance mode. Just wanted to add the idea to the wall.

Related Issue

[lyz-code]

Hi @stdedos thanks for taking the time to open an issue. I don't fully understand your request, can you explain it a little further? I'm not aware of pytest's addopts feature.

I'm not sure if you saw it, but autoimport already supports configuration through the toml file.

PS: Even though we're in maintentance mode it's always good to do requests! Maybe other autoimport users want to implement it :)

[stdedos]

Hi @stdedos thanks for taking the time to open an issue. I don't fully understand your request, can you explain it a little further? ...

I should've been more "templated", I guess 😅

User Story / Feature: When a repo's user wants to run autoimport ..., in that specific repo autoimport should instead run autoimport --ignore-init-modules ... automatically, without requiring the user to type it.

Workarounds: I could've setup myself an alias, I guess

The reason I opened a request is that pytest's addopts "routinely" pops up, and makes me feel

... I'm not aware of pytest's addopts feature.

I should've been less lazy also 😅

Here's pytests addopts configuration explained https://docs.pytest.org/en/latest/example/simple.html

I'm not sure if you saw it, but autoimport already supports configuration through the toml file.

I did. My issue is, though, I haven't seen non-[tool.autoimport.common_statements] configuration options ... configured, so idk if, e.g. ignore-init-modules = true is enough/being picked up, or not

[lyz-code]

Now I see what you mean, thanks for being so throughout.

Checking the code, I see that indeed --ignore-init-modules is not handled by the configuration file, and it only works as a command line argument which is misleading. I'd say to properly fix this issue we should improve the configuration management to something similar of what we have in yamlfix so that all configurations work either through command line arguments, environmental variables or toml configuration files.

I feel that's cleaner than the addopts solution. Nevertheless addopts looks simpler to implement and is more flexible, so I'd be fine with that solution if people are lazy to do it the "cleaner" way.

Until it's fixed I suggest you follow the ugly alias path :(