As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
Wani and I spoke with our VP of Product today about this. The decision has been made to make the SDK source available but the timeline for making that operational has not yet been identified. He is considering what we can do for you in the meantime. I'll update this as soon as we know something.
> Can you tell how this affects your development process?
> makes dev much harder
* No visibility of the SDK API (contract) other than docs
* No way to figure how code functions other than docs or support
* Impossible to debug in the browser without source code + maps
* Impossible to track down bugs and raise issues for you, let alone Pull Requests (fixes)
All the other suppliers I looked at provide the client SDK as an open source project. As it is you provide a wrapper but not the internals.
I am looking into this. I will get back to you shortly.
Can you tell how this affects your development process?
So to partially answer my own question, I guess it not private as I can read the source in the distributed file. However it would be better to have source (and sourcemaps).
For now I just wanted to see if your observables really where RxJS. I see they are, probably 4.0. Plus I wondered how much of the big monster you include :)
Is it private? If so can you make it public? Thanks