You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not easy to access the metadata files, because Symfony only is capable of resource links from one Bundle to another. So simply importing the meta data files from some kind of "not-bundle" library will not work here.
If you have any good ideas how to refactore the loading of the meta data files to enable use cases like yours, PRs are very welcome.
A possible solution would be to generate fixture files from external services (archives, other repositories, etc.). This feature would enable the VipxBotDetectBundle to register its own meta data folder and to load external data into this one. However this is not implemented yet, but something I have on the ToDo list for the vipx/bot-detector library.
Another solution I can think of would be to develop an own file path format for bot meta data files, which can be imported into your own files. But I would not like to add extra conding conventions not part of the current Symfony eco system.
#Importing extended list. You have to choose right path from the current directory to the library's fileimports:
- { resource: '../../../../../../vendor/vipx/bot-detect/Vipx/BotDetect/Resources/metadata/extended.yml' }#Custom botsbots:
amazon_client:
agent: Google-HTTP-Java-Clientip: nulltype: bot
How can I use custom bot list together with basic or extended bot list?
The text was updated successfully, but these errors were encountered: