Make it possible to have some namespaces to NOT be processed by default

[pellared]

Maybe it would be good to have some namespaces that by default are not processed (like signalr, aspnetcore, etc).
They would need to be added explicitly in the config.

CC @jsuereth

[lquerel]

If I understand your request correctly, this is already supported. You can refer to the following example: https://github.com/jsuereth/semantic-conventions-java/blob/475a041a92dfc8cb5ea618456d8d4e992b1c273d/buildscripts/templates/registry/java/weaver.yaml

The params section allows you to define parameters like excluded_namespaces, and the predefined JQ filters already account for them. If you’d like to define additional conditions or filters, the system is usually flexible enough to support them without requiring changes to Weaver’s code.

Let me know if you had something different in mind. Thanks!

[pellared]

I propose to add included_namespaces and have it possible to mark namespaces to be excluded by default.
It would be easier if technology-specific namespaces were included explicitly.

[lquerel]

To mark namespaces to be excluded by default, we could either add a default weaver.yaml configuration in the defaults directory, which is already present in the Weaver repo, or provide a default weaver.yaml file containing the namespaces to exclude. Users could place this file either in their ~/.weaver/ directory or in the parent directory of the one containing the templates. The Weaver configuration will automatically merge based on the rules described here.

Currently, the configuration overriding process does not support removing items from a list, but this feature could be added. For instance, let’s say you have the following declaration in the parent directory of your templates:

# weaver.yaml in parent directory or ~/.weaver/
params:
  excluded_namespace:
    - ios
    - signalr
    - aspnetcore
    - ... 

What you're asking for could be implemented with a "negative" override (a feature not yet supported) as follows:

# weaver.yaml in template directory
params:
  excluded_namespace$remove:
    - signalr

This would remove the signalr namespace from the excluded list.

Alternatively, another approach could be to use a different parameter and implement more complex logic in the JQ filters.