Running modes in coala-quickstart about coala-quickstart HOT 14 OPEN

agree but we'll have to find a better name for sections_only, maybe like allow-incpmplete-sections or so

from coala-quickstart.

We don't need to differentiate then right? we will just send all the bears to user and ask for their settings. did I understood the question correctly?

Ah, okay... So the interaction is very similar to CLI interaction in quickstart.

The intermediate coafile only has sections with bear names and then we can ask for non-optional settings in the web interface, right?

from coala-quickstart.

Then ask users for the optional/non-optional settings of those bears, and send this to the backend saving it in a settings.json file.

How are we going to ask users for the non-optional setting values 😅

from coala-quickstart.

from coala-quickstart.

coala.io already has the name of settings of all the bears (coala.io/languages), we can hence attach input fields to setting name,

For eg, suppose the backend returns,

relevant_bears = ['SpaceConsistencyBear']

Then we show the user a form and take inputs,

 allow_trailing_whitespace ____
 indent_size enforce_newline_at_EOF ___
 tab_width use_spaces ____

And then send these to the backend.

from coala-quickstart.

I see, approach seems good to me
one last doubt though, "What happens after the input values are taken in and ".coafile" is generated?" (do we run coala in non-interactive mode or do we display interactive results on the web like we do in the CLI)

from coala-quickstart.

Also not sure if it's relevant but here's what I had in my GSoC proposal

Integrating coala-quickstart into coala’s try online feature:
This would allow users to use the capabilities of coala-quickstart without having to install it. User inputs the github repository URL and a “placeholder_coafile” gets automatically committed to the repository. While performing analysis locally, coala will detect the placeholder_coafile and prompt the user for the non-optional settings and finally generate the complete coafile. The placeholder_coafile is generated after bypassing all the prompts for non-optional setting values in the characters and filling them with a sentinel value. Another add-on to this feature can be to commit the shell script to install the bear-dependencies as well.

from coala-quickstart.

Let me know what do you think of this, Presently acquire_settings function is passed as a parameter to coalib's fill_setting() by coala-quickstart to get input for settings (https://github.com/coala/coala-quickstart/blob/master/coala_quickstart/generation/Settings.py#L109). Then acquire_settings() calls the require_settings() function which keeps prompting on the coala-quickstart's console for bear settings input.

We can make a function in ConsoleInteraction acquire_settings_from_json() , on the lines of acquire_settings, which will take such json as parameter, and instead of calling require_settings, acquire_settings_from_json() will take the values from this json

bears_settings = {
"PEP8Bear" : {},
"PyLintBear" : {}.
"SpaceConsistencyBear" : { "use_spaces" : true }
}

from coala-quickstart.

Sorry why do you want to ask the user for settings and pass them to coala-incremental? This doesn't make sense at all; quockstart is a tool to auto generate settings and not to run coala, where's the point in giving it settings? And it already has a ci mode.

from coala-quickstart.

Revamped Approach after Discussion

from coala-quickstart.

The plan is to add two options in quickstart, a --dir option to receive current project directory as command line argument, and --sections_only option to generate a coafile with useable as well as unusable bears in CI mode. Presently it only generates one with useable bears in --ci mode, ie, bears not having non optional settings)

from coala-quickstart.

Sounds nice :) Just couple of doubts :P

--sections_only option to generate a coafile with useable as well as unusable bears in CI mode

How would you differentiate between a usable and unusable bears in the coafile? I think we'll have to come up with a syntactical representation in "intermediate-coafile" to mark and identify the sections with unusable bears while parsing.

Also, what is the difference between "coala online" and "webservices" :P (to me it seems like one is "frontend" and other one is "backend")

from coala-quickstart.

Right now it removes the unusable bears with a function that specifically does this tasks. Unusable bears here implies those bears which will ask for setting, so that is why they are unuseable in normal CI mode. But with --ci + --allow-incomplete-sections mode (sections-only), no bears will be removed, that is why we will get unusable + usable bears. We don't need to differentiate then right? we will just send all the bears to user and ask for their settings. did I understood the question correctly?

Actually webServices has an endpoint editor, which we use to trigger coala, this endpoint + the frontend required for this endpoint is 'coala Online'.

from coala-quickstart.

from coala-quickstart.