Privacy changes are changing ids on ctitest

[woodkri]

Displayed id becomes https://sandbox.credentialengineregistry.org/resources and ctid: resources. Ctid appears to be correct in the console, and id is something like https://sandbox.credentialengineregistry.org/resources/1552933010416

[eddavies]

This seems to be working now. However, changing privacy of frameworks on ctitest can cause the editor to freeze, especially with big frameworks.

[Lomilar]

Optimization of this will occur with Eduworks/ec#22

[Lomilar]

Just to check, are we using the asynchronous modes of functions to do encryption? They are much much much faster.

[woodkri]

I have the synchronous versions in there now, I'll look into using the Ec async helper to speed this up.

[woodkri]

Now uses async methods, should be much faster than before. Some changes are still needed to make sure the concept scheme displays the correct concepts in the lefthand pane without duplicating any, but there are other issues open for that. The actual encryption/decryption appears to be working.

[eddavies]

The duplication is no longer occurring but running into an error where competencies are disappearing. Below is a screenshot of where I created a new framework then copied over 160 competencies from an existing framework then attempted to make the framework private:

Additional console errors:

[woodkri]

This seems to be occurring where there are special symbols - in the case of the 68W framework I linked several competencies and had no trouble making my new framework private. When I linked a competency with a TM symbol though, all the competencies disappeared from the left panel and I got the same console errors Eddie posted above. We'll need to look into how these symbols are encrypted/decrypted.

[woodkri]

@eddavies I created a new issue for that since it's probably going to involve some bigger changes. Can you do some privacy testing on data that doesn't have any symbols and let me know if you find any other issues?

[eddavies]

Don't seem to be finding any. Will open a new issue if some are found.

[Lomilar]

Fixes for special symbols are on their way.