Does ignore_only work?

[megasuperlexa]

I am using the following section in my buf.yaml

lint:
  use:
    - MINIMAL
  ignore_only:
    ENUM_VALUE_PREFIX:
      - integrations
      - "clients/*"
      - internals/**

but whichever format I am using, files from integrations, clients and intenals are still produce same linting errors about enums. I am using this guide https://buf.build/docs/configuration/v1/buf-yaml#ignore_only
Where I guess foo and bar are directory names?

[megasuperlexa]

turns out I have to have a buf.yaml in every directory of my repo, this way it works

[megasuperlexa]

This is exactly what I am trying to evade - changing all imports in all files. Besides, I still do not understand the limitation - if the files are in the same folder, why not shorthand it to just the filename? Code generator seem to understand this.

[bufdev]

Importing from a common directory is effectively a prerequisite for modern Protobuf development. One or two plugins may understand this (I'm not terribly familiar with the .NET setup), but most of the plugin ecosystem won't operate properly if you don't have your imports derive from a common location - Protobuf as a language requires unique file paths based on their import path, so as soon as you have two files in your entire company's API corpus named "common.proto" that are imported as such, you won't be able to make progress.

A discussion for why this is the case is outside the scope of this issue, but suffice to say we'd highly recommend importing from a common directory for your continued success with Protobuf as your usage grows. Buf effectively enforces this paradigm.

[megasuperlexa]

I see. So in my case I think it is still the best solution to have a buf module per folder, i.e. a separate buf.yaml + singlebuf.work.yaml because I cannot justify such a massive changes to already working solution (we use .NET, Python and Typescript simultaneously) solely becuse of linter.

[bufdev]

That will work, but as mentioned, it's atypical of modern Protobuf usage, and will lead to problems (including with .NET, Python, and TypeScript) as the number of your Protobuf files continues to grow - you will end up with a conflict in your Protobuf file names at some point.

[megasuperlexa]

@bufdev ok, I have changed my example as per your suggestion. https://github.com/megasuperlexa/buf-example/pull/3/files
Now buf lint works, but buf breaking against main branch does not. As I understand, this is because main branch still contains old format imports.
I tried putting internals folder to ignore section of breaking but this seem to have no effect.
So my understanding is migration should be done in 2 steps: first change imports in main branch and merge, second introduce breaking.

[bufdev]

The issue here is you are using wildcards - buf.yaml can only accept paths to files or directories. Examples:

• foo/bar: ignore everything in the directory foo/bar.
• foo/bar/baz.proto: ignore the file foo/bar/baz.proto.