os/gcfg: priority of env should be higer than file.

[yangyanqing]

Go version

go version go1.23.4 windows/amd64

GoFrame version

2.8.3

Can this bug be reproduced with the latest release?

Option Yes

What did you do?

With v2.8.3, config by file had higher than config by env.

What did you see happen?

func (c *Config) Get(ctx context.Context, pattern string, def ...interface{}) (*gvar.Var, error) {
	var (
		err   error
		value interface{}
	)
	value, err = c.adapter.Get(ctx, pattern)
	if err != nil {
		return nil, err
	}
	if value == nil {
		if len(def) > 0 {
			return gvar.New(def[0]), nil
		}
		return nil, nil
	}
	return gvar.New(value), nil
}

What did you expect to see?

In general, config by env should have higher priority than config by config.yaml.
Spring cloud and viper think so too.

[gqcn]

@yangyanqing Yes, I think so too. It should be updated in method GetWithEnv and GetWithCmd for package gcfg:

• gf/os/gcfg/gcfg.go

  Line 121 in 6ea1526

  func (c *Config) GetWithEnv(ctx context.Context, pattern string, def ...interface{}) (*gvar.Var, error) {

• gf/os/gcfg/gcfg.go

  Line 143 in 6ea1526

  func (c *Config) GetWithCmd(ctx context.Context, pattern string, def ...interface{}) (*gvar.Var, error) {

Thanks for your proposal!

[github-actions]

Hello @yangyanqing. We like your proposal/feedback and would appreciate a contribution via a Pull Request by you or another community member. We thank you in advance for your contribution and are looking forward to reviewing it!
你好 @yangyanqing。我们喜欢您的提案/反馈，并希望您或其他社区成员通过拉取请求做出贡献。我们提前感谢您的贡献，并期待对其进行审查。