-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BE] Support assets/
paths
#37
Comments
Hi, how can we test it? @gnespolino |
It's released on dev and test environments, so yes. We also added Inail to the repo lists |
from dev or test I cannot see inail assets, I can only see the changes in the PR. |
we added support for asset/** folder, leaving the legacy folder name support. |
I just triggered an harvesting manually both on dev and test, result should be visible in a couple of minutes. |
can you confirm this are the url: Still didn't see anything from inail, so far. |
Good morning @Clou-dia, let me finish some work on it (there was a naming error in the vocabularies folder). I'll ping you when it's ready. |
@gnespolino è risolto? |
yes, legacy paths are still supported as well. |
Verified, thanks |
I expect
To harvest first following paths:
assets/{ontologies,vocabularies,schemas}
Instead
It only procesesses ontopia-like paths
Ontologie,VocabolariControllati
Possibili soluzioni
Extend the static class to support both, considering that Ontopia-like paths are a legacy.
A configuration parameter has been considered and excluded.
The text was updated successfully, but these errors were encountered: