gitea: Error while getting .editorconfig file

So maybe the proposal could be: “Make Gitea not report user’s editorconfig syntax error as repository notice”, or only show the syntax error on the proper page clearly.

Yes, https://github.com/go-gitea/gitea/pull/21257 got stalled. I think it’s the right solution to parse graceful and display errors. Ideally the admin page could also show the affected repo, or the admin notice could also be removed entirely.

Hmm, logging these parser “warnings” might be hard to consume. How about adding a warnings slice to a parse result, e.g.?

type Editorconfig struct {
  Root        bool
  Definitions []*Definition
  config      *Config
  warnings    []string
}

Fatal errors should still return err of course.

On a related note, according to https://stackoverflow.com/a/57682840/808699, YAML 1.2 dropped the yes/no on/off aliases, so I think it’s probably wise to follow and be strict about true/false/unset, which is also in-line with the spec.

@silverwind agreed. Most of them, could be moved to an error as log.