-
Notifications
You must be signed in to change notification settings - Fork 11
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
feat: introduce standalone mode #162
Conversation
getSidebarContainerStyle(): string { | ||
if (this.disableBackend) { | ||
return "top: 53px;"; | ||
} | ||
return "top: 85px;"; | ||
} |
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.
Hm, I wonder if we should instead add a disable-backend
CSS class, and use that to guard the CSS rules, instead of this?
@@ -48,13 +52,24 @@ export class NetzgrafikApplicationComponent { | |||
.subscribe((params) => { | |||
uiInteractionService.setEditorMode(EditorMode.NetzgrafikEditing); | |||
uiInteractionService.showNetzgrafik(); | |||
versionControlService.load(params.getVariantId(), true); | |||
try { |
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.
Is there a reason why this is a try
/catch
instead of a if (disableBackend)
?
getLayoutContentStyle(): string { | ||
if (environment.disableBackend) { | ||
return "height: 100%;"; | ||
} | ||
return ""; | ||
} |
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.
Ditto: could use a CSS class here instead.
authConfig: AuthConfig; | ||
backendUrl?: string; | ||
authConfig?: AuthConfig; | ||
disableBackend: boolean; |
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.
We've been wondering whether it would make more sense to drop the disableBackend
field, and instead make it so a null backendUrl
means that the backend is disabled. Personally I think that'd make sense since backendUrl
is nullable.
7977c4a
to
29ff459
Compare
Co-authored-by: adrian_egli <adrian.egli@gmail.com> Co-authored-by: Simon Ser <contact@emersion.fr>
Co-authored-by: Louis Greiner <greiner.louis@gmail.com>
29ff459
to
6b50c72
Compare
…doesn't work correctly. This fix resolves the issue.
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 part can be merged
Thank you! |
* feat: introduce standalone mode Co-authored-by: adrian_egli <adrian.egli@gmail.com> Co-authored-by: Simon Ser <contact@emersion.fr> * feat: register as a custom element Co-authored-by: Louis Greiner <greiner.louis@gmail.com> * fix: easy return * small fix - the use of ng-container embeded in the sbb-icon-sidebare doesn't work correctly. This fix resolves the issue. --------- Co-authored-by: Louis Greiner <greiner.louis@gmail.com> Co-authored-by: adrian_egli <adrian.egli@gmail.com>
Description
This is the first part of #158, cleaned-up and rebased.
This is missing inputs/outputs for
AppComponent
: that work will come as a second follow-up PR once this one is merged.The normal behavior of the application remains the same (
ngsscbuild
has not been modified, only scripts to trigger newstandalone
environment have been added)Checklist
documentation/