Can't this be solved by just setting the correct self.default_path in the constructor and not changing anything else?

hold on a bit I was working on an alternative implementation

alternative implementation

• re-work multi --styles-file #14707

Can't this be solved by just setting the correct self.default_path in the constructor and not changing anything else?

Yes... except for in an edge case: Here is an example. If I have 3 styles files named "my.csv", "my_anime.csv" and "my_realistic.csv" I would naturally use "my*.csv" in the command line to load these. In this case the default file will be "my.csv" rather than "styles.csv".

If, when loading all files matching the wildcard there hadn't been a "my.csv" file there we do indeed fall back to "styles.csv".

alternative implementation

• re-work multi --styles-file #14707

👀

Can't this be solved by just setting the correct self.default_path in the constructor and not changing anything else?

Yes... except for in an edge case: Here is an example. If I have 3 styles files named "my.csv", "my_anime.csv" and "my_realistic.csv" I would naturally use "my*.csv" in the command line to load these. In this case the default file will be "my.csv" rather than "styles.csv".

If, when loading all files matching the wildcard there hadn't been a "my.csv" file there we do indeed fall back to "styles.csv".

But can't you do what you described in constructor and set self.default_path correctly?

@w-e-w #14707 looks good to me. Ran through my own use-cases and all seems fine.

@w-e-w #14707 looks good to me. Ran through my own use-cases and all seems fine.

thanks good to hear