[
https://issues.apache.org/jira/browse/NIFI-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942252#comment-15942252
]
ASF GitHub Bot commented on NIFI-814:
-------------------------------------
GitHub user trixpan opened a pull request:
https://github.com/apache/nifi/pull/1624
NIFI-814 - Introduce hidden header with name of Processor to allow th…
…ose arriving to site via direct reference to know the name of the processor
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [X] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Is your initial contribution a single, squashed commit?
### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [X] ~~~Have you written or updated unit tests to verify your changes?~~~
- [X] ~~~If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?~~~
- [X] ~~~If applicable, have you updated the LICENSE file, including the
main LICENSE file under nifi-assembly?~~~
- [X] ~~~If applicable, have you updated the NOTICE file, including the
main NOTICE file found under nifi-assembly?~~~
- [X] ~~~If adding new Properties, have you added .displayName in addition
to .name (programmatic access) for each of the new properties?~~~
### For documentation related changes:
- [X] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/trixpan/nifi NIFI-814
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1624.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1624
----
commit 5c3dff85ca33354bde1b0f92bcb96c4ea2bfc77a
Author: Andre F de Miranda <[email protected]>
Date: 2017-03-26T10:42:39Z
NIFI-814 - Introduce hidden header with name of Processor to allow those
arriving to site via direct reference to know the name of the processor
----
> Published processor usage guides on the web should have a title
> ---------------------------------------------------------------
>
> Key: NIFI-814
> URL: https://issues.apache.org/jira/browse/NIFI-814
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Reporter: Aldrin Piri
> Assignee: Andre F de Miranda
> Priority: Trivial
>
> Since documentation has been published, it is handy that search engines index
> the processor pages. When clicking on one of these pages directly, the
> processor is not shown in context of the frame as typically provided via the
> help in application and there is no title on the document.
> For example:
> https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.GetHTTP/index.html
> Would be nice if it had a header that said it was GetHTTP instead of scouring
> tabs for the name in the title or scanning through the URL (any of which may
> be compressed/unviewable depending on browser layout).
> The one consideration is that this title is provided in the in-app help when
> a component is selected which would make adding the title to the processor
> usage redundant in that scenario.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
