-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add docs for coalang #51
Comments
From @hypothesist on March 6, 2016 6:0 @AbdealiJK Currently there are zero bears using coalang. So it's in a very volatile stage, I'd say (there is an open issue to change the whole structure, I just made a PR to change from spaces to underscores everywhere, ...). I think we should wait just a bit more before putting it in the official docs since it may change frequently. |
From @abhsag24 on March 6, 2016 6:35 @AbdealiJK we do package it now, bear writers may go ahead and use it without the documentation anyway , i say we document it, but advise the bear writer that this is subject to change |
From @sils1297 on March 6, 2016 9:15 Agreed
|
From @AbdealiJK on March 6, 2016 9:38 Unblocking it then |
From @Makman2 on March 6, 2016 16:6 At least my doc-extraction stuff works very good, there won't change much inside the current stuff. |
Currently coalangs are usecase specific, not sure this issue is necessary now^^ |
From @AbdealiJK on March 6, 2016 5:56
coalang seems to be becoming more and more popular right now.
We have 2 issues blocked by it and it will probably become popular as we've depleted the list of linter based bears we want.
We should document it properly (once it actually stabilizes to some extent). I find lots of questions coming up about it in gitter.
@abhsag24 @hypothesist would love to know whether you think coalang is stable enough for this. If you think it's not, we should add the blocked label to this issue for now until its stable enough.
Copied from original issue: coala/coala#1816
The text was updated successfully, but these errors were encountered: