Skip to content

Create Entry.md #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
arekbal wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

Create Entry.md #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/Entry.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
WIP

### Entry

There is often a Time where given API action requires multiple steps to be fulfilled.
One of the more prominent examples would be removong items from a prefilled container, where user would first have to check if given record exists in the container and then again look it up to remove it. That problem of extra unnecesarry lookup is easy to mitigate by a) adding more (composite)operations to the API like FindRemove, AddOrUpdate, and sometimes b) pretend the operation is happening but let the user know when it didn't, such as bool Remove(item) does.
First solution leads to API explosion of sorts.
This design of separate operations composited outside of API might lead to many annoying problems
Even in most basic example above - our code would have to find :While that is quite straightforward operation which is often exposed as joined operation add_overwrite