beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-199) Improve fluent interface for manipulating DisplayData.Items
Date Tue, 26 Apr 2016 23:28:12 GMT


ASF GitHub Bot commented on BEAM-199:

GitHub user swegner opened a pull request:

    [BEAM-199] Update DisplayData APIs to make overrides more understandable

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

You can merge this pull request into a Git repository by running:

    $ git pull displaydata-api

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #247
commit 6a63fc6dd536be49971dc4987cc0d0ab3f887829
Author: Scott Wegner <>
Date:   2016-04-25T23:04:38Z

    Change API to register DisplayData items to make overrides more understandable


> Improve fluent interface for manipulating DisplayData.Items
> -----------------------------------------------------------
>                 Key: BEAM-199
>                 URL:
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-java-core
>            Reporter: Scott Wegner
>            Assignee: Scott Wegner
>            Priority: Minor
> See discussion [here|].
The current fluent API may be difficult to use and could cause some ambiguity. We have some
ideas in the linked thread on how to improve it.

This message was sent by Atlassian JIRA

View raw message