Kari Ikonen
Kari Ikonen
This came with REPL case
that would be nice if feasible Also being able to start breakpoint as disabled could be useful, i.e. setup them via .rdbrc startup script and enable when needed
Relying purely into logic in this gem may not be futureproof solution. Due to that might make sense to integrate core logic with established service. To allow full user control...
Values in both ignore and include path lists can be [String | Regexp | Proc]. So I would suggest trying either Regexp or Proc to accomplish this.
Since dokku is different platfoem than heroku, failures there can be non heroku issue related. Secondly, any traces, logs?? My first suspect with dokku is that needed dependencies for ngannotate...
Could you try locally with compiled assets to see how it works (see readme)
Updated to latest ngannotate; however, I don't believe it encounters your trouble.
So, what you get if you do this ``` NG_FORCE=true RAILS_ENV=development bundle exec rake assets:clobber assets:precompile NG_FORCE=true rails s -p 3001 ```
Hm.. should have remembered to notify that for full assets precompile test locally, tou need to modify environments/development.rb. see readme for info.
Q: what traces you see in development.log. there should be some "ng-xxxx" traces there.