connect interactive window (repl) to entire project
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- developer-experience, tooling
Research direction
Start by reproducing the C# interactive-window workflow described here: navigate to a namespace, invoke the database setup function, and determine how DLL dependencies are currently supplied. Compare that behavior with the Clojure REPL's (in-ns 'my-db-namespace) flow and its compile-before-start requirement. Done means the project can expose the requested namespace-level dependencies without manually including every DLL, with the expected interactive behavior defined.
Written by the indexing model from the issue text.
Description
Is there a way to navigate to a namespace and start using db or other server functions without having to include every dependency?
The Clojure repl allows you to call (in-ns 'my-db-namespace) and then I can call my database setup function. All dependencies are include when you navigate to the namespace. Currently, it looks like I have to include all .dlls when I am in a c# namespace. Is this feature possible? However, the Clojure repl compiles the program first before the interactive dev environment starts.
Thanks
- Dominant language
- C#
- Stars
- 78
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 dotnet/interactive-window
-
dotnet/interactive-window#255 · 2 comments · 6 reactions · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dotnet/interactive-window#241 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
dotnet/interactive-window#230 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dotnet/interactive-window#185 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dotnet/interactive-window#184 ·
All issues in dotnet/interactive-window
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·