Simon Mumenthaler

The necessary change, to actually skip the `onload` event listener in the ssr html is to provide the additional `inlineCriticalCss` property when using the `ngExpressEngine`: ```javascript server.engine('html', ngExpressEngine({ bootstrap: AppServerModule,...

@paragbhingre Thank you for investigating this problem. I receive the error in different repos. The action works when running on master but fails on our `#\d+-[a-z\d-]+` branches. The config I...

Problem still exists - is there any fix?

I guess you'd integrate it with the @DateProperty decorator. To still support custom DateTypes we would need to have the default constructor of the date class (or a provided function)...

Hi @jthomerson @mariobittencourt see [lab/#278-model-instance](/shiftcode/dynamo-easy/tree/lab/%23278-model-instance) I basically just return `Object.assign(new modelConstructor(), model)` where `model` is the plain data object (the one returned until now). This way the values are defined...

@mariobittencourt you can use the published prerelease version `@5.7.0-pr278.1` to test this approach

hi @roni-frantchi We never had the need for this feature and right now there are other issues we'd like to address first. But of course we're open for PRs :)...

Hi @nolde To support an async `TableNameResolver` function a lot of refactoring would be necessary. **But:** since the `TableNameResolver` is called every time a new Request instance is created (eg....

same here. We use specific content types for header and footer config; the user could basically break it by renaming the respective stories. It would be a big improvement to...

+1 It would make it way easier to handle the case where various components need to have a specific set of properties.