Skip to content
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.

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

Extract data access layer #124

Merged
merged 14 commits into from
Aug 21, 2024
Merged

Extract data access layer #124

merged 14 commits into from
Aug 21, 2024

Conversation

WULCAN
Copy link
Collaborator

@WULCAN WULCAN commented Jul 30, 2024

I think I want the data access layer just for the overview of the interactions with server state.

This change set contains some first steps towards a data access layer. I would like it reviewed before I continue as there are multiple small but non-trivial decisions made.

I recommend review commit-by-commit and consulting the commit messages for more detail.

WULCAN added 11 commits July 29, 2024 22:24
First access data, then extract props.
First access data, then extract props.
* Destructure parameter directly
* Infer type variable to fit long line
Use expression body instead of block body.
* Shorter parameter and property names
* Inline constants
* Use expression body
WULCAN added 3 commits August 18, 2024 16:50
MDN uses a captial F in its name for the parameter.
Instantiating objects with new can be a little ambigious. For example
new X().Y() is either creating a new instance with X as a constructor or
with Y as a constructor.

Being nameable, factory functions are also better than constructors when
you want to offer multiple different signatures for creating instances.
It is more important to highlight that the field has a different type
than that the field too contains promises.
@WULCAN WULCAN merged commit 0159801 into main Aug 21, 2024
1 check passed
@WULCAN WULCAN deleted the issue-25/data-access-layer branch August 21, 2024 19:25
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.

2 participants