Skip to content

Conversation

@JulesGresset
Copy link
Member

@JulesGresset JulesGresset commented Jun 26, 2025

…ngredientsForecast method to handle use case logic

Describe your changes

Add useCase=POS on ingredientsForecast to return the populated elements of the ingredients.

How to test the feature

call ingredientsForecast route with useCase=POS query param

Issue ticket number and link

Closes #177

Checklist before requesting a review

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have performed a self-review of my code
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Documentation has been updated as required
    If a single item in this checklist is not checked, the pull request cannot be accepted

@JulesGresset JulesGresset requested a review from Xantass June 26, 2025 21:59
@JulesGresset JulesGresset self-assigned this Jun 26, 2025
@JulesGresset JulesGresset linked an issue Jun 26, 2025 that may be closed by this pull request
@JulesGresset JulesGresset enabled auto-merge June 26, 2025 22:00
@JulesGresset JulesGresset merged commit aa16168 into dev Jun 27, 2025
13 checks passed
@JulesGresset JulesGresset deleted the 177-add-usecase-to-ingredientsforecast branch June 27, 2025 09:28
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

Successfully merging this pull request may close these issues.

Add useCase to ingredientsForecast

3 participants