Skip to content
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

Possible file name conflict #3

Open
cyrill-martin opened this issue Sep 30, 2020 · 2 comments
Open

Possible file name conflict #3

cyrill-martin opened this issue Sep 30, 2020 · 2 comments
Assignees

Comments

@cyrill-martin
Copy link
Member

IF a user would upload two data and/or rule files with the same name but different content, the service will override one of the files while temporarily saving them.

@cyrill-martin cyrill-martin self-assigned this Sep 30, 2020
@hanscools
Copy link

Isn't the path taken into consideration to avoid that?

@cyrill-martin
Copy link
Member Author

Isn't the path taken into consideration to avoid that?

Unfortunately not. I currently create a JSON object to send the file selection to the microservice with only the following for each file:
{
"file": [here comes the filename],
"content": [here comes the content of the file]
}

The service accepts this data and temporarily creates files to do the reasoning session with EYE.

To avoid any conflicts, I can add something to each filename before saving them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants