typeprof 0.15.2 → 0.20.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c31fc03c67fa15924e901b70890318e2391fa58cfaf897e51ff6a00d673d792a
-  data.tar.gz: c6ce703ec1c5f8a41d04603162746adb8a9416ccf29abc8ef1441cf83a3b41e3
+  metadata.gz: bacf4fa5ea4b9d22be05ade768e45b4a3e86f8845e6e470775d9c9333e72e5ad
+  data.tar.gz: 186ed39f8e38d58bf710cea41942eaff66bc9ca505560e67a6f43d7ce6790896
 SHA512:
-  metadata.gz: 790815f2528442ae742df0c3576a97ff6d2c856db374f2c8a63bb965dd6c715b6fa686d84b1fd56683e938e9c8e4014e9e86b53bb34ca4e9975b93bb5e5188df
-  data.tar.gz: ecc1433a74aebbe31c267c4697d71389a841cd66d74b251d1cc2d22bbeca228f141a8861ecbeebee3b16d54a8397f41eeab4f1f25ebac42103aee5e1146c9fe6
+  metadata.gz: 3f67fb359672f245991f71b50475ff6a472f2db67ab8c3e508a4bea7ff89155a407b8de9747e64444f2c79f78311305018951eeae896ddab594b8ceca864b67f
+  data.tar.gz: ade3c4b52badc09023a669ea4fc1d10d66dc80ae35f4e65c8a92cb25d851701d6d79f135589c99f24b650da8fc863761911c450b5cb660ea93b6562ac18e6881

data/.github/workflows/main.yml

@@ -7,7 +7,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        ruby-version: [2.7, 3.0, head]
+        ruby-version: [2.7, 3.0,head]
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v2

data/Gemfile.lock

@@ -1,8 +1,8 @@
 PATH
   remote: .
   specs:
-    typeprof (0.15.1)
-      rbs (>= 1.3.1)
+    typeprof (0.20.2)
+      rbs (>= 1.6.2)
 
 GEM
   remote: https://rubygems.org/
@@ -11,7 +11,7 @@ GEM
     docile (1.4.0)
     power_assert (2.0.0)
     rake (13.0.1)
-    rbs (1.3.3)
+    rbs (1.6.2)
     simplecov (0.21.2)
       docile (~> 1.1)
       simplecov-html (~> 0.11)
@@ -19,7 +19,7 @@ GEM
     simplecov-html (0.12.3)
     simplecov_json_formatter (0.1.3)
     stackprof (0.2.17)
-    test-unit (3.4.2)
+    test-unit (3.4.4)
       power_assert
 
 PLATFORMS

data/doc/ide.md

@@ -0,0 +1,81 @@
+# How to use TypeProf for IDE
+
+First, try it with an already-configured repository!
+
+1. `rbenv install 3.1.0-dev`
+2. `git clone https://github.com/mame/rbswiki`
+3. `cd rbswiki && bundle install`
+4. `rbs collection install`
+5. install [VSCode extension for TypeProf](https://marketplace.visualstudio.com/items?itemName=mame.ruby-typeprof) to your VSCode
+6. open the `rbswiki` folder by VSCode
+7. open `lib/rbswiki/wiki.rb`
+
+If everything goes well, you will see guessed signatures for each method:
+
+![Screenshot](typeprof-for-ide.png)
+
+### Troubleshooting
+
+* Make sure that you are using ruby 3.1.0-dev.
+
+```
+$ ruby -v
+ruby 3.1.0dev (2021-09-28T11:03:54Z master 545e01645f) [x86_64-linux]
+```
+
+* Check if typeprof version is 0.20.0 or later.
+
+```
+$ bundle exec typeprof --version
+typeprof 0.20.0
+```
+
+* Check if TypeProf can analyze `lib/rbswiki/wiki.rb` within one second.
+
+```
+$ bundle exec typeprof lib/rbswiki/wiki.rb
+warning: rbs collection is experimental, and the behavior may change until RBS v2.0
+# TypeProf 0.20.0
+
+# Classes
+module RBSWiki
+  class Wiki
+    @content: Hash[String, String]
+...
+```
+
+* See the log of "Ruby TypeProf" in vscode's "OUTPUT" panel.
+
+![Log of TypeProf for IDE](typeprof-for-ide-log.png)
+
+## How to configure TypeProf for your code
+
+1. Write `gem "typeprof"` to your `Gemfile`, and run `bundle install`
+2. Write `rbs_collection.yaml`, and run `rbs collection install`
+3. Test if TypeProf works well by running `bundle exec typeprof your_code.rb`
+4. Open your repository with vscode
+
+### Troubleshooting
+
+*TBD*
+
+## Protips, limitation, unimplemented features, ...
+
+TypeProf for IDE is extremely preliminary! Please give it a try with a warm heart...
+
+* Write a simple (type-level) test in each file with `if $0 == __FILE__` guard to guide TypeProf to infer method signatures.
+* Use `require` only for loading gems. To load your code, use `require_relative` instead of `require`. (Or, create `bin/typeprof` and pass `-Ilib`. TBD for details)
+* Currently, TypeProf for IDE loads `typeprof.rbs` at the top folder. (I'll need to improve it to read `sig/` directory)
+* TypeProf for IDE analyzes each file within one second. Unfortunately, it takes very long to analyze big code, or complex code, or code that requires a big gem. In this case, TypeProf for IDE cannot show any guesses. Splitting a file or manually writing RBS may make the analysis faster. (TBD for details)
+* Unfortunately, TypeProf may report some false positive errors that you cannot stop. I'll create an option to configure error level.
+* TypeProf for IDE tries to invoke TypeProf as follows:
+    * If your repository has `bin/typeprof` executable, it is invoked.
+    * Otherwise, it will try to invoke a command specified in VS`typeprof.server.path`.
+    * Otherwise, it will try to invoke `bundle exec typeprof`.
+    * Otherwise, it will try to invoke `typeprof`.
+    * Otherwise, TypeProf for IDE gives up.
+* Some people says TypeProf for IDE works with vim! (TBD for details)
+
+## How to develop TypeProf for IDE
+
+See `../vscode/development.md`.

data/exe/typeprof

@@ -3,4 +3,8 @@
 require_relative "../lib/typeprof"
 
 config = TypeProf::CLI.parse(ARGV)
-TypeProf.analyze(config)
+if config.options[:lsp]
+  TypeProf.start_lsp_server(config)
+else
+  TypeProf.analyze(config)
+end