Open anelad opened 5 years ago
@osnoser1 you as an expert of SSR can you give me your opinion here?
@dianjuar I'm always thrilled with your response time 🔥 🤣
@anelad Do you have a repo of your problem ? I can tell you that I kwon what SSR is about but I don't have any code experience with that
I can create a basic git repo. But I'm afraid its gonna take some time since I'm highly busy right now.
Sorry for the delay @dianjuar. I created a PR with the fix: #19 😄
@dianjuar @osnoser1 I think there is no need for a repo of the problem now?
@osnoser1 THANK YOU!!!! I just ask for your opinion and you ended up making a PR! What a such friend! Thank you so much
@dianjuar @osnoser1 I think there is no need for a repo of the problem now?
I think there is no longer necessary
@anelad deploying...
Thank you @dianjuar
@osnoser1 take a look at this ----> https://travis-ci.org/bikecoders/ngx-sticky When installing the dependencies is compiling something and fails installing it... Do you know the reason ?
@anelad I just publish the package with your solution on the @next
tag.
You can install it by npm install ngx-sticky-directive@next
I am having issues with travis ci that, it's design to make the deployment automatically but is failing installing some dependencies. So until I fix that awful CI you can make your test with that version of the package.
I will reopen the issue until I fix it. Please tell me how it goes.
Sorry for the delay on this.
@osnoser1, We're migrating this package to Nx and making compatibility with Angular9.
I know too little about SSR, could you give us the instructions to know how to unit test the feature that you added? I want to have this feature always present on every change that we made from now on. I want to have the unit test for it.
@dianjuar one of the ssr problems it's complex test that feature, in fact it is in the TODO of Angular Universal as you can see here.
I would have to think how to implement unit tests to the feature. Tomorrow I review the source code of this project to think of a good strategy.
@osnoser1 that was the information that I needed please don't mind.
And how test it manually? The reason for my concern is that we are migrating to Nx #25 and I want to at least test it manually.
The first thing is first; it works on SSR.
But gives console errors on page loads.
At first load of the app; it gives
ReferenceError: window is not defined
. Full output:When surfing between pages after the app is loaded, it gives
ERROR ReferenceError: document is not defined
. Full output: