-
Notifications
You must be signed in to change notification settings - Fork 5
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
Replicate changes from mongo driver to json driver #37
Comments
On 9 April 2013 09:03, Juan Martin Runge [email protected] wrote:
that is basically:
Niv Sardi |
Agree! Enviado desde mi BlackBerry -----Original Message----- On 9 April 2013 09:03, Juan Martin Runge [email protected] wrote:
that is basically:
Niv Sardi Reply to this email directly or view it on GitHub: |
This depends on #44 |
status? On 11 April 2013 15:08, Tomas Neme [email protected] wrote:
Niv Sardi |
Status @Lacrymology ? I think #44 was solved already... |
Do we keep the JSON driver? |
no if we have a replacement as a test harness to test the rest of the code. On 17 September 2013 17:07, Tomas Neme [email protected] wrote:
Niv Sardi |
hm, all I can say right now is that current tests go through 46% of mongo playlists driver, but nothing of json driver I'm not sure what we're testing or not testing with(out) going through any playlists drivers. Parts of the functional test (specifically the ones that depend on the playlist driver) are not running yet (because they will depend on changes in caspa) |
I would like to keep the JSON driver. Its not only a way to test mosto, 2013/9/17 Tomas Neme [email protected]
|
If it's only for mosto without caspa we let it die,... The overhead is toó Again, either we do the same with our test harness or we fix it. Niv Sardi, mobile.
|
I think there is no overhead... let me take a look at it and write its 2013/9/18 Niv Sardi [email protected]
|
Replicate all changes made to mongo driver into json driver, in order to keep them changeable.
The text was updated successfully, but these errors were encountered: