Is it a waste of time submitting documentation fixes?

[Neutrino-Sunset]

Core Library

MSAL.js (@azure/msal-browser)

Wrapper Library

MSAL Angular (@azure/msal-angular)

Public or Confidential Client?

Public

Documentation Location

https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular/docs/initialization.md

Description

I submitted a fix for one of your broken documentation examples here

It's been closed by someone who didn't seem to understand the issue, and who is now not responding to comments.

Your guidelines suggest that if we find an issue in the documentation to submit a PR instead of opening an issue, but if this is going to be the response then obviously that's just a waste of time.

[CO97]

This might have put the final nail in the coffin for this library for me.

The daily frustration I have had since trying to implement this library across multiple Angular applications has been the worst I have ever had. Between the lack off and confusing documents to random nuances between different workflows that are not explained at all.

How the library is intended to be consumed is also not ideal, some random observables to subscribe too put into root levels of the application that perform some magic.