-
Notifications
You must be signed in to change notification settings - Fork 9
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
asearch
function usage
#149
Comments
I think it's just the matter of obsolete documentation. |
The documentation is to be updated. P Dnia 30.11.2015 o godz. 14:20 Witold Chodor notifications@github.com napisał(a):
|
OK, I understand. |
Would be great if you can take care of it. 2015-11-30 16:14 GMT+01:00 Witold Chodor notifications@github.com:
pozdrawiam serdecznie, |
@pbiecek |
@MarcinKosinski @pbiecek |
There's an issue for default parameter in createEmptyGithubRepo: Why asearch won't work with default=TRUE argument in createEmptyLocalRepo? 2015-12-01 18:04 GMT+01:00 Witold Chodor notifications@github.com:
|
Because of |
So maybe createEmptyRepo with default=TRUE should also change global 2015-12-01 18:15 GMT+01:00 Witold Chodor notifications@github.com:
|
Do you mean to put
in createEmpty Repo' body? |
like this:
|
if deafult == TRUE ? 2015-12-01 18:54 GMT+01:00 Witold Chodor notifications@github.com:
|
So, like this ?
|
Looks good. Pleas do the change and submit PR 2015-12-01 18:58 GMT+01:00 Witold Chodor notifications@github.com:
|
Why do we need 'type = aoptions("type")' ? it is actually a possible vulnerability since default value of type may not 2015-12-01 17:56 GMT+01:00 Witold Chodor notifications@github.com:
pozdrawiam serdecznie, |
Regarding the 'default' parameter (let's use separate issues for separate 2015-12-01 18:04 GMT+01:00 Witold Chodor notifications@github.com:
pozdrawiam serdecznie, |
The fact that you need to synchronise changes in 'type' and 'repoDir' is an 2015-12-01 19:01 GMT+01:00 Marcin Kosiński notifications@github.com:
pozdrawiam serdecznie, |
I understand your point of view. |
@pbiecek |
Alterations in `asearch` and other functions due to #149 issue.
Thanks, |
When it comes to
|
Ok looks good. If this is fixed, can you @wchodor close the issue? |
@pbiecek
I am in the course of reviewing
asearch
function and I'm wondering what was your goal. Were you planning to extend its functionality on local repository? This part ofasearch
function's body indicates that we want to search and read from local repo too. But it can be only default local repo.I am a little bit confused because the documentation suggests that we want to work on Github Repository only.
The text was updated successfully, but these errors were encountered: