When seeding the database, a local pictogram folder is created, however, when it is run through the new Docker functionality, the pictogram folder is created in the docker environment, and not locally, which means that few integration tests fails, as they are dependent on the local pictogram folder.
Furthermore, it is likely that any request to the web-api that relates to pictograms either does nothing or crashes the web-api.
The quick-fix currently used, is that all pictograms are added to GitHub, thereby ensuring the folder i present after the repository have been cloned, however, arguably it would be preferred to not upload all pictograms to GitHub.
Possible Suggested Solution
Find a solution to creating the folder locally, when running the Docker environment.
Re-add that pictograms are ignored on pull requests in the .gitignore.
Description
When seeding the database, a local pictogram folder is created, however, when it is run through the new Docker functionality, the pictogram folder is created in the docker environment, and not locally, which means that few integration tests fails, as they are dependent on the local pictogram folder. Furthermore, it is likely that any request to the web-api that relates to pictograms either does nothing or crashes the web-api.
The quick-fix currently used, is that all pictograms are added to GitHub, thereby ensuring the folder i present after the repository have been cloned, however, arguably it would be preferred to not upload all pictograms to GitHub.
Possible Suggested Solution