Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 800FC11F81 for ; Mon, 22 Sep 2014 07:49:32 +0000 (UTC) Received: (qmail 52488 invoked by uid 500); 22 Sep 2014 07:49:31 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 52425 invoked by uid 500); 22 Sep 2014 07:49:31 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 52403 invoked by uid 99); 22 Sep 2014 07:49:31 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Sep 2014 07:49:31 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id E41F8948391; Mon, 22 Sep 2014 07:49:30 +0000 (UTC) From: garrensmith To: dev@couchdb.apache.org Reply-To: dev@couchdb.apache.org References: In-Reply-To: Subject: [GitHub] couchdb-fauxton pull request: Added missing API link to header of ... Content-Type: text/plain Message-Id: <20140922074930.E41F8948391@tyr.zones.apache.org> Date: Mon, 22 Sep 2014 07:49:30 +0000 (UTC) Github user garrensmith commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/60#issuecomment-56339457 @benkeen thanks for trying to fix this. That fix is not quite right. The way to fix this is actually just to add a `masterLayout.apiBar.show();` after this line https://github.com/apache/couchdb-fauxton/blob/master/app/addons/fauxton/base.js#L88 How this section works is that in each RouteObject we have a `apiUrl` function which has a documentation link and a raw api link. In the fauxton module we listen for the routeObject `renderComplete` event. We look at the routeObject and see if it has a `apiUrl` function and then render the api url for the page. @robertkowalski only on the database page do we have two api bars. Its definitely not ideal and in the long term we must fix it. But we can only do that once we have moved all the components from #31 into master. Then we can refactor some of those new components to use the single master api bar like it use to be. --- 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 feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---