We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Im asking my self how flexible is the current pre validation of the asset uploader also in regards to other domains.
Two things allready jumped into my mind by looking at the code and try it out.
Is it necessary to check the readme file in the asset?
Reading the asset definition in the readme file potential dataprovider are flexible by adding optional files. Why are we checking a fixed number here?
envited-x-data-space/apps/envited.ascs.digital/common/validator/shacl/shacl.test.ts
Lines 22 to 25 in e6a1918
The text was updated successfully, but these errors were encountered:
@jeroenbranje magic number in code?
Sorry, something went wrong.
jdsika
jeroenbranje
No branches or pull requests
Im asking my self how flexible is the current pre validation of the asset uploader also in regards to other domains.
Two things allready jumped into my mind by looking at the code and try it out.
Is it necessary to check the readme file in the asset?
Reading the asset definition in the readme file potential dataprovider are flexible by adding optional files. Why are we checking a fixed number here?
envited-x-data-space/apps/envited.ascs.digital/common/validator/shacl/shacl.test.ts
Lines 22 to 25 in e6a1918
The text was updated successfully, but these errors were encountered: