PHOENIXCONTACT / PHOENIXCONTACT/MORYX-Framework
Do not raise update events for products / recipes which were not changed
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 57
- Forks
- 39
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 36
Description
Is your feature request related to a problem? Please describe.
Currently, if you save a recipe within the product UI the the facade throws events for all recipes of the product and the type itself. There is no option to only save the modified recipe. The other way around, if a product gets saved, recipe updates for all recipes are raised.
Describe the solution you'd like
- The product management / recipe management can identify changes and only for the changed entries the event will be raised
Describe alternatives you've considered
- The UI can identify the changes and only call save for the changed entries
Originally proposesd here
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the product and recipe management save operations through the facade and identify where events are emitted for products, recipes, and their types. Compare both save directions described in the issue. Done means unchanged entries no longer raise update events, while changed entries still do.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100