Fork me on GitHub
#proton
<
2016-08-05
>
dvcrn01:08:22

@gabe: like you would in normal atom. Just put the configuration strings inside .proton instead of atom config and just active the linters layer

gabe02:08:20

@dvcrn the README for linter-tslint shows configuration:

'linter-tslint':
  # Custom rules directory (absolute path)
  rulesDirectory: "/path/to/rules”

gabe03:08:29

I’ve got this in my .proton file:

["linter-tslint" {"rulesDirectory” “/path/to/rules"}]

gabe03:08:39

under configuration

dvcrn03:08:15

Ah yeah that is not well documented, apologies. That would be

["linter-tslint.rulesDirectory" "/path/to/rules"]

gabe03:08:45

great. thx!

dvcrn03:08:53

let me know if it worked!

gabe03:08:43

@dvcrn: i think that was the wrong configuration option

gabe03:08:03

do i just add a dot for every level of object nesting?

gabe03:08:05

turns out there was no config for what i wanted. i ended up just putting the config in my project directory

gabe03:08:15

thanks for your help @dvcrn

dvcrn03:08:30

correct, just a dot for every level until the last object. clojurescript datatypes will get parsed into javascript ones

dvcrn03:08:41

what do you mean with "turns out there was no config for what I wanted"?

gabe03:08:57

I was trying to specify a global tslint.json file

gabe03:08:25

linter-tslint doesn’t have that option

gabe03:08:56

nor can you configure the linter in config.cson/.proton

dvcrn03:08:07

ok got it, thanks for clarifying

gabe03:08:09

everything’s working now though

geksilla07:08:52

can you put STR for this one?

geksilla07:08:34

I was trying to reproduce this but didn't hit this error

dvcrn07:08:03

Let me see if I can reproduce it again. I just pulled your code, compiled with dev and this happened

geksilla07:08:54

nevermind, just reproduced it

geksilla07:08:31

I turned on wipe configurations and got this error

geksilla07:08:26

will fix it soon. Thanks

geksilla07:08:11

atom 1.9 is pretty nice. I like performance improvements, so switched back to atom )

geksilla08:08:28

btw I hit issue with build/dev-repl, something wrong with namespaces errors like

Uncaught Error: goog.require could not find: proton.lib.helpers
Uncaught Error: goog.require could not find: proton.layers.base
etc.

geksilla08:08:59

after shadow build update to 1.0.215 dev-repl works fine

dvcrn08:08:52

There are too many editors these days. Atom has the best ecosystem but is tooooooo sloooooooow

dvcrn08:08:22

I started playing with sublime again and it's so fast. I even ported some very tiny things from proton back to it

dvcrn08:08:11

But mainly keep jumping between atom and vim 😛

geksilla08:08:12

looks very nice