ceres, branch 0.3.x-to-0.4.y Recipe server for your favorite dishes https://cgit.xengineering.eu/ceres/atom?h=0.3.x-to-0.4.y 2024-05-26T10:16:27Z tools: Create standalone program for 0.4 migration 2024-05-26T10:16:27Z xengineering me@xengineering.eu 2024-05-26T08:46:05Z urn:sha1:05a525f27971541ee5f86c97d8a45cf48c371621 Update CHANGELOG.md for version 0.4.0 2024-05-17T21:29:34Z xengineering me@xengineering.eu 2024-05-17T21:29:34Z urn:sha1:08150821fdb8fd1af23d84e661e61983a16a36b5 model: Add strict Ingredient.Validate() 2024-05-17T21:20:41Z xengineering me@xengineering.eu 2024-05-15T18:18:39Z urn:sha1:bc149ee58122effc9d4c035da2af3a7ec1f2f862 model: Add strict Step.Validate() 2024-05-17T21:16:36Z xengineering me@xengineering.eu 2024-05-15T18:18:13Z urn:sha1:f8f5d296f218f79646a54d3aed8d54fa9f8704c1 model: Fix another unhandled error 2024-05-17T21:15:56Z xengineering me@xengineering.eu 2024-05-17T21:15:56Z urn:sha1:5194ea4b29ffef0fe5206899243339cf109af41d This could also lead to bugs. model: Fix ignored error 2024-05-17T21:10:17Z xengineering me@xengineering.eu 2024-05-17T21:08:05Z urn:sha1:5d5580285a366e37ac00a4e1a6f2f1bda853ff28 An ignored return value here caused a serious bug as soon as validation for ingredients was tried. The validation could raise an error e.g. on a negative amount for the ingredient. This error was ignored at the changed line which resulted into deleted ingredients for the whole recipe. model: Rework recipe validation 2024-05-17T15:14:40Z xengineering me@xengineering.eu 2024-05-17T15:12:50Z urn:sha1:5eca3267d37cdc51f775b5452727efebbb7e7e9e This reduces code duplication and enforces time stamps. view: Fix time stamp bug 2024-05-17T15:14:35Z xengineering me@xengineering.eu 2024-05-17T15:06:55Z urn:sha1:0416f520cff9716792ac0f3ade5f71187d07ac2e The recipe edit page HTML template did not contain the two time stamps "Created" and "LastChanged" as hidden form values. Thus the information was not passed from the backend to the frontend. On a save the recipe without time stamp information was injected into the backend. This effectively deleted any time stamp information. This commit fixes that bug by including all fields of the model.Recipe struct inside the form of the recipe-edit.html template. view: Use number input for ingredient amount 2024-05-17T15:14:29Z xengineering me@xengineering.eu 2024-05-17T13:51:45Z urn:sha1:c61e45a5a260d9804ebc4f54814edf1e1b471ac3 This accepts only real numbers with a minimum step of 0.001 as input for the amount field of a recipe ingredient. The browser has the chance to give the user direct feedback that a non-numeric string will not work. view: Remove empty ingredient summaries 2024-05-15T18:42:09Z xengineering me@xengineering.eu 2024-05-15T18:42:09Z urn:sha1:d14aece3295405b4377ea20aabd9c621aace4922 If the recipe has no ingredients at all the "Ingredient summary:" text used to be displayed. This is not useful and confusing. It is removed with this commit. model: Make Recipe.Validate() more strict 2024-05-15T18:09:35Z xengineering me@xengineering.eu 2024-05-15T18:09:35Z urn:sha1:ae771a44c2ffe31dc1bd67a12b65849f7d7d2d11 Before the next release this method should be as strict as possible to avoid cases where actually invalid enters databases. view: Require text for steps 2024-05-15T17:39:17Z xengineering me@xengineering.eu 2024-05-15T17:39:17Z urn:sha1:34880a0194f66e2b1808b45abfb01497d4816aaf It does not make sense to add empty steps. view: Require ingredient type 2024-05-15T17:37:05Z xengineering me@xengineering.eu 2024-05-15T17:37:05Z urn:sha1:29c8c305c52b97248e505cdfc6b86e96f57d0a53 It does make sense to add an ingredient only with a type and no amount or unit like 'salt'. But it does not make sense to add an ingredient without a type like '5' or '2 l'. view: Update to simple.css v2.3.0 2024-05-15T17:33:11Z xengineering me@xengineering.eu 2024-05-15T17:33:11Z urn:sha1:45a0a10c070e3dba33be01d4de4d094fd7f7394a This is the latest available release. Updated to keep up to date and adopt fixes. view: Rename to 'Ingredient summary:' 2024-05-15T17:27:05Z xengineering me@xengineering.eu 2024-05-15T17:27:05Z urn:sha1:b48f4514a44450da1ad5da68ce434c2b87e721d0 This used to be named 'Ingredients: which might be confusing since ingredients are defined per step and the list at the top of the recipe is just a summary. When adding a recipe step or an ingredient the browser should focus on 2024-05-15T17:20:01Z xengineering me@xengineering.eu 2024-05-15T17:20:01Z urn:sha1:d8b40f0a0a2ac2bcb8b9b690166ae7594c067298 the first text input of that new element. This supports using Ceres without a mouse and only with tab-based navigation with a keyboard. Update CHANGELOG.md 2024-05-14T19:25:31Z xengineering me@xengineering.eu 2024-05-14T19:25:31Z urn:sha1:dfee08b810d2c8ec5883dc8e8ec8a143abd2e961 view: Complete ingredient editing 2024-05-14T18:43:41Z xengineering me@xengineering.eu 2024-05-14T18:14:42Z urn:sha1:a87128138bdb301ede64049ec5068e47abb5c839 view: Add HTML for editing recipe ingredients 2024-05-13T19:52:48Z xengineering me@xengineering.eu 2024-05-13T19:51:43Z urn:sha1:b5b72880a0b6e9f188b532c9b2ad360ff1dab2ea view: Add ingredient overview to recipe read page 2024-05-12T18:52:25Z xengineering me@xengineering.eu 2024-04-07T10:04:11Z urn:sha1:bf328dd38a28cf44cfa81c7f1dcd95936d2d0301 view: Show ingredients on read page 2024-05-12T18:52:25Z xengineering me@xengineering.eu 2024-04-07T09:56:20Z urn:sha1:01d97189d245300d65ca31d650dd868d1d1fc0d8 model: Add per-step ingredients 2024-05-12T18:52:25Z xengineering me@xengineering.eu 2024-04-04T12:54:21Z urn:sha1:87ae71413e47ef34da57bc1e0b8dddbf84b0c66a view: Use HTML template to add recipe steps 2024-05-12T18:38:24Z xengineering me@xengineering.eu 2024-05-12T18:38:24Z urn:sha1:fec2fea87615e6ee3a6e73f7f98e021eee1b7098 This makes the JS function way simpler and removes a duplication of the step HTML code. view: Create new html/recipe-step.html 2024-05-12T18:20:14Z xengineering me@xengineering.eu 2024-05-12T18:20:14Z urn:sha1:64ece1c4455ed6f8e8be5cb8f060f14b6131823f This allows to use it in two places: - template for loop for backend-generated steps - a HTML template tag for frontend- / JS-generated steps view: Move all JS code to static/ceres.js 2024-05-12T18:06:17Z xengineering me@xengineering.eu 2024-05-12T18:06:17Z urn:sha1:f2800e8289e9637bb3227a5f9622edabf6529b0f view: Remove global JS code in recipe-edit.html 2024-05-12T18:01:02Z xengineering me@xengineering.eu 2024-05-12T18:01:02Z urn:sha1:cfeff398f0ad7e4205dc26b66ca2b46ebca24606 This makes it impossible to move the whole JS functionality into the central ceres.js script. Moving that JS code there makes caching possible and bundles all JS-related code in one file. The overall goal is to get rid of as many JS code as possible. Move config path from config to flags struct 2024-05-11T22:12:55Z xengineering me@xengineering.eu 2024-05-11T22:12:55Z urn:sha1:642fed1cbf5160c89a93deab810bd44fb49d2a4a This is metadata about the config and thus does not belong to the config itself. Moving it to the struct holding flag values is straight forward since it is defined by flags. Group flag variables in struct 2024-05-11T22:03:56Z xengineering me@xengineering.eu 2024-05-11T22:03:56Z urn:sha1:938ab103727688b73f2d7b3ef4d9e1b1c85c6628 view: Add unit test for index handler 2024-05-11T21:08:42Z xengineering me@xengineering.eu 2024-05-11T21:08:42Z urn:sha1:907bd7e63f4cf3cb01bc678e09fc5b8962afe750 Inject examples only with new --example flag 2024-05-09T20:37:03Z xengineering me@xengineering.eu 2024-05-09T20:33:42Z urn:sha1:0ac3cc76b4b6c824c4b3f7a357d40b487984abfb The default use case should be to not inject example recipes.