foreign function interface in KRL so that rulesets can use JavaScript modules
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, typescript
Research direction
Start by defining how KRL rulesets would import JavaScript modules and how the engine would load modules and their dependencies. Clarify whether URL-based imports are supported and how failures from missing dependencies should be reported; the feature is done when these behaviors are specified and implemented.
Written by the indexing model from the issue text.
Description
Phil
Today at 9:33 AM
Idea: foreign function interface in KRL so that rulesets can use JavaScript modules. Any exported function world be importable. (edited)
👍
1
3 replies
Phil
32 minutes ago
One question would be how the module (and its dependencies) would be loaded into the engine so it’s available.
Phil
31 minutes ago
This would allow mixed programs of KRL and JS and allow KRL programs to make use of existing JS modules without having to modify the engine to load them.
Phil
24 minutes ago
JS imports can be urls. So we could limit modules to only those that load dependencies from urls. But I’m not sure how we do that to arbitrary depth. I guess then it’s the developers problem. We just report that a module can’t be loaded because dependencies can’t be found.
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from Picolab/pico-engine
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Picolab/pico-engine#668 ·
-
1 - Ready bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Picolab/pico-engine#496 ·
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
Picolab/pico-engine#666 ·
-
documentation question
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Picolab/pico-engine#662 ·
-
help wanted
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Picolab/pico-engine#661 · 2 comments ·
All issues in Picolab/pico-engine
Similar issues
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Potential Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Comfy-Org/ComfyUI_frontend#23773 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
lingdojo/kana-dojo#34301 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/gh-aw-firewall#11797 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#7007 ·
Maintainers usually reply within 1 day