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

Refactor services into layers #2212

Merged
merged 8 commits into from
Feb 14, 2024
Merged

Refactor services into layers #2212

merged 8 commits into from
Feb 14, 2024

Conversation

hannobraun
Copy link
Owner

The concepts of layers has been in the air for a while. See #2116 and #2117, for example. And I've actively been working towards this for a few weeks now, in #2117 specifically.

As part of that work, I've had lots of opportunity for thinking and experimenting (#2117 wasn't as easy as hoped, and required lots of design work). At some point during that process, I realized something: We already have layers. They are called "services", and they were added for a different reason, but they actually fit the design I was homing in on pretty perfectly.

In addition, "services" is a shitty name. Too generic, to the point of being meaningless. So this pull request renames them to "layers". This lays the foundation for adding new layers in the future, as part of the issues I've linked above, and others.

@hannobraun hannobraun enabled auto-merge February 14, 2024 09:59
@hannobraun hannobraun merged commit b01a209 into main Feb 14, 2024
4 checks passed
@hannobraun hannobraun deleted the layers branch February 14, 2024 10:02
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.

1 participant