issue_609

[jj105]

No description provided.

[jj105]

Hi, Jon.
I edited code to fix issue_609.
but on my environment, it takes too long time (more than an hour) to create a new applet.
I think it loads too many resources.

[jj105]

Can you please tell me what should I do to make process of creating a new applet run faster?

[shnizzedy]

Can you please tell me what should I do to make process of creating a new applet run faster?

It's an open epic and in my opinion, the current weakest link in the whole project. On my machine, it takes ~1‒2 seconds per JSON-LD document to load a protocol, so for testing I just choose smallish protocols, like reproschema:protocols/mindlogger-demo/mindlogger-demo_schema, which still takes several minutes.

See also #625 (comment)

[shnizzedy]

This PR resolves #609!

@jj105 ― This PR is based on 66c752c which predates #637 which resolved an environment issue causing integration tests to fail. If you merge recent changes into your branch (f64fe00c978e48606a26ecd18fa01bb3150c419e) or rebase your changes onto a more recent commit (539830c643c3a4fbcbc29ff984fbc9382de526fa), your code passes the CI tests.

The changelog would also need to be updated prior to merging.

@binarybottle @WorldImpex @henryrossiter @hotavocado @devbtech ― I leave it to y'all if you like this applet naming strategy or if you want to make changes, but the bones are in place in this PR:

[shnizzedy]

We only have ~28% coverage of the Python core in this codebase as of a8ba865, but I'd argue that's no reason not to include tests with new functionality.

Write a test

The output of GET /user/applets?role=coordinator&unexpanded=true will be an Array of Objects in which applet["http://www.w3.org/2004/02/skos/core#prefLabel"]["@value"] will be the display name of an applet.

― #645 (comment)