This looks really cool!

I'm trying this on a leiningen project (
https://github.com/jumarko/clojure-experiments/) but I'm getting a NPE:
            Reflector.java:  426  
clojure.lang.Reflector/invokeNoArgInstanceMember
                 utils.clj:   11  clindex.utils/normalize-path
                 utils.clj:   10  clindex.utils/normalize-path
...
                      REPL:  280  
clindex.scanner/eval22432/scan-namespace-decl
               scanner.clj:  354  clindex.scanner/scan-namespaces/fn
                  core.clj: 2755  clojure.core/map/fn
              LazySeq.java:   42  clojure.lang.LazySeq/sval
              LazySeq.java:   51  clojure.lang.LazySeq/seq
                   RT.java:  535  clojure.lang.RT/seq
                  core.clj:  137  clojure.core/seq
             protocols.clj:   24  clojure.core.protocols/seq-reduce
             protocols.clj:   75  clojure.core.protocols/fn
             protocols.clj:   75  clojure.core.protocols/fn
             protocols.clj:   13  clojure.core.protocols/fn/G
                  core.clj: 6828  clojure.core/reduce
                  core.clj: 6810  clojure.core/reduce
               scanner.clj:  313  clindex.scanner/merge-namespaces
               scanner.clj:  309  clindex.scanner/merge-namespaces
               scanner.clj:  358  clindex.scanner/scan-namespaces
               scanner.clj:  346  clindex.scanner/scan-namespaces
                   api.clj:  142  clindex.api/index-project!
                   api.clj:  128  clindex.api/index-project!
                      REPL:   11  
clojure-experiments.parsers.clindex/eval22438

It looks like the `meta` on `ns-decl` returns nil here: 
https://github.com/jpmonettas/clindex/blob/master/src/clindex/scanner.clj#L278

Is that something that's a result of my setup (using leiningen)?



On Monday, 4 November 2019 13:37:49 UTC+1, Juan Monetta wrote:
>
> https://github.com/jpmonettas/clindex
>
> Clindex is a general and extensible Clojure[Script] source file indexer.
>
> It scans a Clojure[Script] project together with all its dependencies and 
> generates a datascript database with facts about them.
>
> It is intended to be used as a platform for building dev tools so they 
> don't have to deal with the complexities of understanding Clojure code by 
> reading the filesystem.
>
> Instead as an api for talking about your code it gives you a datascript db 
> full of facts you can use together with d/q, d/pull, d/entity, etc.
>
> --
> Juan Monetta
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojure/813542d3-fced-41ae-b5bd-c74113adde94%40googlegroups.com.

Reply via email to