Include list of skipped results of component discovery

[lluisoxigen]

Describe the issue

New docker weblate installation with version 5.2.1. Add Component works correctly. But on saving Component discovery, it shows "No matching components were found!". In the same path, it should have to discover 30 files more.

The setup is the following:

Regular expression to match translation files against
web_areapersonal_companyname/Resources/Views/Empleado/(?P<component>[^/]*)\.(?P<language>[^/.]*)\.resx

File format
.NET resource file

Customize the component name
{{ component }}

Define the monolingual base filename
web_areapersonal_companyname/Resources/Views/Empleado/{{ component }}.resx

Language filter
^[^.]+$

File mask
web_areapersonal_companyname/Resources/Views/Empleado/EmpleadoBandeja.*.resx

Monolingual base language file
web_areapersonal_companyname/Resources/Views/Empleado/EmpleadoBandeja.ca.resx

Gitlab repository file examples
https://gitlab.companyname.com/informatica/test_weblate/-/blob/develop/web_areapersonal_companyname/Resources/Views/Empleado/EmpleadoBandeja.ca.resx
https://gitlab.companyname.com/informatica/test_weblate/-/blob/develop/web_areapersonal_companyname/Resources/Views/Empleado/EmpleadoPerfil.ca.resx

I already tried

• I've read and searched the documentation.
• I've searched for similar issues in this repository.

Steps to reproduce the behavior

No response

Expected behavior

No response

Screenshots

No response

Exception traceback

No response

How do you run Weblate?

Docker container

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

[nijel]

Define the monolingual base filename web_areapersonal_companyname/Resources/Views/Empleado/{{ component }}.resx

It is missing .ca, I guess the file without a language code doesn't exist.

Monolingual base language file web_areapersonal_companyname/Resources/Views/Empleado/EmpleadoBandeja.ca.resx

[github-actions]

This issue has been marked as a question by a Weblate team member. Why? Because it belongs more to the professional Weblate Care or community Discussions than here. We strive to answer these reasonably fast here, too, but purchasing the support subscription is more responsible and faster for your business. And it makes Weblate stronger as well. Thanks!

In case your question is already answered, making a donation is the right way to say thank you!

[lluisoxigen]

Hi nijel! You are right. Now it works as it is expected and all files are detected. Thank you very much. It would be nice if the web would inform on which field the error is.

I leave my final setup in case it can hep someone else:

Regular expression to match translation files against
(?P<originalHierarchy>.*/Resources)/(?P<folders>.*)/(?P<component>[^/]*)\.(?P<language>[^/.]*)\.resx

File format
.NET resource file

Customize the component name
{{ folders }}: {{ component }}

Define the monolingual base filename
{{ originalHierarchy }}/{{ folders }}/{{ component }}.ca.resx

[nijel]

Thanks for the suggestion, adding a list of skipped entries with a reason would be useful for debugging issues like this. ComponentDiscovery.check_valid would return an invalidity reason and ComponentDiscovery.perform would return an additional list of skipped entries.

[github-actions]

This issue seems to be a good fit for newbie contributors. You are welcome to contribute to Weblate! Don't hesitate to ask any questions you would have while implementing this.

You can learn about how to get started in our contributors documentation.

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.