Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/432#issuecomment-104783084
unit-test missing
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
GitHub user benkeen opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/432
Option to show only editor in CodeEditor component
This adds a `showEditorOnly` option to the CodeEditor / component. It
prevents the extra title, beautify markup and wrapper div being
Github user michellephung commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/432#issuecomment-104786104
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user benkeen commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/432#issuecomment-104784391
Yeah I know, but sometimes things are sooo small I must question the
need for the unit test. :(
---
If your project is set up for it, you can reply to
Github user benkeen commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/432#issuecomment-104785407
@robertkowalski, why do I expect your response to be: I find your lack of
faith disturbing.?
---
If your project is set up for it, you can reply to this email
On Fri, May 22, 2015 at 2:37 PM, Alexander Shorin kxe...@gmail.com wrote:
Hi Paul,
Great proposal! Replied inline to preserve context.
Bikeshed First
--
I have no idea what we'd call this. We could repurpose the
couch_plugins app conceivably or make something new. For the the
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/423#issuecomment-104655121
it seems the only remaining buggy test which behaves flaky is
viewCreateBadView
---
If your project is set up for it, you can reply to this email and
GitHub user iilyak opened a pull request:
https://github.com/apache/couchdb-couch-replicator/pull/10
Add a test case for filtered replication
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iilyak/couchdb-couch-replicator
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/423#issuecomment-104671224
changes test was redirecting sometimes before the changes where available
on `_changes` - also fixed
---
If your project is set up for it, you can
Hi Paul and Russell,
Great writeup! Thank you for spending time writing it.
My observation is that proposed API misses few quite important use cases.
So I want to iterate over the proposed API to clarify, improve and add
missing functionality.
But first of all I would like to establish a
priv/*.cfg files if used aren't intended to be configured by users.
They're not part of the external surface area a normal user/sysadmin
should care about. For instance, a recent request from dynamic URL
handlers was to be able to disable specific URL endpoints. The chttpd
app would be responsible
Hi Dulanga,
Probably the easiest (and fastest way) way for us to give feedback would be for
you to open a PR. That way we can comment on the code inline, and we can pull
the repo down and see how it works in our environment faster.
I’ll pull your branch now, and take a look, but if you want
Github user nadeeshaan commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/401#issuecomment-104746546
@robertkowalski , @michellephung , @benkeen
In this branch by mistakenly I have done some alterations while merging
with the master. But I have my
Github user michellephung commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/401#issuecomment-104748483
no worries @nadeeshaan :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Ilya,
Can you go into the specific use cases a bit more? From what I can
tell your proposing that couch_epi is a central nexus of some rather
large swaths of code (ie, replacing the entire API to couch_stats). To
me that's a bit of an anti-goal. I'd much rather keep things simple
and decoupled
Hi Paul,
Great proposal! Replied inline to preserve context.
Bikeshed First
--
I have no idea what we'd call this. We could repurpose the
couch_plugins app conceivably or make something new. For the the
purposes of this document I'll call it couch_epi (for extensible
plugin
16 matches
Mail list logo
