LivelyKernel / LivelyKernel/lively.next
Allow specifying `needsServerInterface` for non-default packages
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
With #703 we have made it possible to headlessly test packages that are non-default packages, aka that are not always loaded.
For those packages, it is currently not possible to let them eval against a server backend.
We need a mechanism to specify the warranted backend somewhere else than in the package-config. Might be that the package.json is a good place.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading #703 and the current package-config path that determines needsServerInterface for non-default packages. Compare it with package.json handling and the existing headless testing flow. Done means non-default packages can specify the warranted server backend and evaluate against it during headless tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100