We are currently working on the problems with links added dynamically and they should be resolved in next version.

For now please try to use ViewChild decorator to get access to navbar component methods in your ts file, then create a method that will hide the navbar and add it to (click) event of the logout button.

Here is an example:

<mdb navbar #navbar></mdb-navbar>

@ViewChild('navbar') navbar: NavbarComponent;

hideNavbar() {
  if (this.navbar.shown) {
    this.navbar.hide();
  }
}

Sorry for the delay Arkadiusz. The links are within the component, yes. I'm showing and hiding different links asynchronously based on state.auth in the OnInit Lifecycle hook.

app.component.html

<links>
<ul class="navbar-nav mr-auto">
  <li class="nav-item active" *ngIf="isLoggedIn$ | async">
    <a [routerLink]="['/home']"
      class="nav-link waves-light"
      mdbWavesEffect>Home<span class="sr-only">(current)</span></a>
  </li>
  <li class="nav-item" *ngIf="isLoggedOut$ | async">
    <a [routerLink]="['/auth/login']"
       class="nav-link waves-light"
       mdbWavesEffect>Login</a>
  </li>
  <li class="nav-item" *ngIf="isLoggedOut$ | async">
    <a [routerLink]="['/auth/register']"
       class="nav-link waves-light"
       mdbWavesEffect>Register</a>
  </li>
  <li class="nav-item" *ngIf="isLoggedIn$ | async">
    <a (click)="logout()"
       class="nav-link waves-light"
       mdbWavesEffect>Logout</a>
  </li>
</ul>
<form class="form-inline waves-light" mdbWavesEffect>
  <div class="md-form my-0">
    <input class="form-control mr-sm-2" type="text" placeholder="Search">
  </div>
</form>

There is a closing link tag. This editor strips it out

app.component.ts

ngOnInit(): void {
this.isLoggedIn$ = this.store.pipe(
  select(isLoggedIn)
);

this.isLoggedOut$ = this.store.pipe(
  select(isLoggedOut)
);
// Stop the spinner
this.spinner.stop();

}

We will take a closer look at it to check if there are any problems with the component code.

Does the user log out by clicking on the link that is inside navbar 'links' component? If so, is this logout link generated dynamically after the navbar component has already rendered?