_delete methods against entities with non generated IDs can cause issues

[whistlinjoe]

Created a competency with the id: "https://credentialengineregistry.org/navy/resources/ce-72058167-4666-4e1e-b3db-8fa342a39f3e"

Running the following script generated a CORS issue:

var c = EcCompetency.getBlocking("https://credentialengineregistry.org/navy/resources/ce-72058167-4666-4e1e-b3db-8fa342a39f3e");

EcRepository._delete(c, null, function(p1) {console.log("Item deleted...");});

Access to XMLHttpRequest at 'https://credentialengineregistry.org/navy/resources/ce-72058167-4666-4e1e-b3db-8fa342a39f3e' from origin 'http://localhost:63342' has been blocked by CORS policy

[Lomilar]

In this case, you are working with an aliased piece of data. The repository you're working on is not credentialengineregistry.org.

As such, we need to delete the data that is stored in a specific repository.

That is done via:

repo.deleteRegistered(c,success,failure);