Generate clear message when recipe exists during creation

[christianlupus]

Closes #690

[codecov]

Codecov Report

Merging #702 (09661c9) into master (2fbdea8) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

❗ Current head 09661c9 differs from pull request most recent head 6da7ae8. Consider uploading reports for the commit 6da7ae8 to get more accurate results

@@             Coverage Diff             @@
##             master    #702      +/-   ##
===========================================
- Coverage      0.95%   0.95%   -0.01%     
- Complexity      458     461       +3     
===========================================
  Files            18      19       +1     
  Lines          1460    1472      +12     
===========================================
  Hits             14      14              
- Misses         1446    1458      +12     

Flag	Coverage Δ	Complexity Δ
integration	0.00% <0.00%> (ø)	461.00 <1.00> (+3.00)
unittests	0.95% <0.00%> (-0.01%)	461.00 <1.00> (+3.00)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ	Complexity Δ
lib/Controller/MainController.php	0.00% <0.00%> (ø)	41.00 <0.00> (+1.00)
lib/Controller/RecipeController.php	0.00% <0.00%> (ø)	15.00 <0.00> (+1.00)
lib/Exception/RecipeExistsException.php	0.00% <0.00%> (ø)	1.00 <1.00> (?)
lib/Service/RecipeService.php	0.00% <0.00%> (ø)	241.00 <0.00> (ø)

[christianlupus]

@seyfeb I am getting some strange errors. It seems I have tomatoes on my eyes. Can you have a quick glance if you see the culprit?

I get this error:

to corelate the line numbers, here the debugger's output

Can you explain why the exception is passed on to the browser although it is caught?

[seyfeb]

I pulled the PR and can't reproduce this behavior. I get the XHR error but no other. Maybe you need to clear your cache?

[christianlupus]

The issue is merely esthetical. The main functionality is given as far as I see.

In a new browser (private window), the issue persisted. Also rebuilding using npm run build did not solve it. What else could it be? The node.js version (14 for me)?

Eventually, I could try to use the zip file from the GH actions to see if this is something with my machine/build setup.