-
Notifications
You must be signed in to change notification settings - Fork 7
Screen layout commands and expanded documentation #296
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
base: release/3.0.0
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be merged but I think it would be beneficial to work more cleanly with available vs installed templates and layouts.
Logic for checking if a template or layout is installed is spread througout leading to code that is harder to follow and debug than necessary. I think it should be possible to consolidate that logic in the two service classes. Thus all other code could call ->getInstalledTemplates|Layouts()
. This way other code would be more readable .
|
||
public function updateScreenLayout(ScreenLayoutData $screenLayoutToUpdate): void | ||
{ | ||
if (null !== $screenLayoutToUpdate->screenLayoutEntity) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A comment about what ->screenLayoutEntity
signifies and the reason for the null check will help us down the road
…:os2display/display-api-service into feature/documentation-and-screen-layouts
Issue
#249
Description
Checklist