what does autoscan do?

[andreineculau]

read https://github.com/nickkolok/paraquire/blob/d438aed4d5e23dd7612870c906fb4e7ff2575c28/etc/autoscan-proposal.md and i'm in the dark completely

is autoscan:true supposed to mean look in package.json paraquire.json ? and autoscan:false doesn't ? I see no point - use that as default, and maybe allow for configs to be altered in the pararequire paraquire.json call.

Secondly, I want to highlight that in my original tweet I said a module pararequire.js paraquire.js (not a json file) https://twitter.com/andreineculau/status/900808960667766784 which makes "For example, I don't know how to put in JSON the following:" redundant. babel, eslint, etc have all introduced js-based configuration because it keeps the world open (you can run code, you can require configs from other files, etc)

[nickkolok]

I.e. you mean that paraquire should use another entry point? I.e. require looks to index.js, paraquire looks to paraindex.js, where should be smth honest like this:

module.exports =
paraquire('./index.js',{builtin:{fs:true}});

?

In this case the dependent should use usual require:

var lib = require('lib/paraindex.js');

[andreineculau]

I somehow get the feeling we're not understanding each other.

1. What should autoscan do?
2. if autoscan is supposed to be a flag to tell paraquire to look up permissions in some well-known configuration file, then I would do without the flag and always do the lookup

[nickkolok]

Yes, unfortunately certain misunderstanding takes place =/
So, let's step thesis by thesis.

Your Thesis 1: library should describe permissions needed for it in special easy-readed file.
Your Thesis 2: this file shoul be .js, not .json
Your Thesis 3: paraquire shoul automatically scan package directory for such a file

Am I right?

[andreineculau]

yup

…

On Fri, Aug 25, 2017 at 6:58 PM, nickkolok ***@***.***> wrote: Yes, unfortunately certain misunderstanding takes place =/ So, let's step thesis by thesis. Your Thesis 1: library should describe permissions needed for it in special easy-readed file. Your Thesis 2: this file shoul be .js, not .json Your Thesis 3: paraquire shoul automatically scan package directory for such a file Am I right? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AArOQW4Xw7FkoQGEF1QtZAL8uKzArO4uks5sbv0zgaJpZM4PCar3> .

-- andreineculau.com <http://www.andreineculau.com>

[nickkolok]

So,
My Thesis 4: this work culd be done by entry point, alternative to index.js. Let's call it paranodex.js.
My Thesis 5: paranodex.js can contain all necessary paraquire calls. List of paraquire calls is fair enough to determine rights used by library.

Do you agree with these?

[andreineculau]

I can m(dis)agree better when i see it ;) Go your own path. At this point I cannot dedicate that much energy to this brainstorming based on the points that i raised in the issues (small ROI), so i think i would influence you negatively

…

-- http://andreineculau.com

On 26 Aug 2017, at 10:58, nickkolok ***@***.***> wrote: So, My Thesis 4: this work culd be done by entry point, alternative to index.js. Let's call it paranodex.js. My Thesis 5: paranodex.js can contain all necessary paraquire calls. List of paraquire calls is fair enough to determine rights used by library. Do you agree with these? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.