Skip to content

Conversation

@swegner
Copy link
Contributor

@swegner swegner commented Apr 28, 2016

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.

@swegner
Copy link
Contributor Author

swegner commented Apr 28, 2016

R: @bjchambers

super.populateDisplayData(builder);

Combine.populateDisplayData(builder, fn, fnClass);
Combine.populateDisplayData(builder, fn, fnDisplayData);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add comments here about the choice of calling populateDisplayData vs. builder.include(...)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added usage comments on DisplayData.Builder#include and HasDisplayData#populateDisplayData-- let me know what you think.

@bjchambers
Copy link
Contributor

In DisplayData can you add details about the difference between builder.include(component) and component.populateDisplayData(builder)? And possibly Javadoc on each that notes those cases and points at the other option.

@swegner
Copy link
Contributor Author

swegner commented Apr 28, 2016

I've addressed all feedback so far. Please take another look. @bjchambers

@swegner
Copy link
Contributor Author

swegner commented Apr 28, 2016

travis failure looks like a flake. I believe this is ready to go.

* <p>Including subcomponent display data via
* {@code DisplayData.Builder.include(HasDisplayData)} ensures that the
* {@link Item#getNamespace() namespace} of registered {@link Item display items}
* is properly set to the namespace of the subcomponent. To register display data from a base
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using {@code include(subcomponent)} will associate each of the registered items with the namespace of the {@code subcomponent} being registered. To register display data in the current namespace use {@code builder.include(subcomponent)} instead.

@see ...

@bjchambers
Copy link
Contributor

Minor wording comments, then LGTM

@swegner
Copy link
Contributor Author

swegner commented Apr 29, 2016

I've addressed all feedback so far. Please take another look. @bjchambers

* Using {@code include(subcomponent)} will associate each of the registered items with the
* namespace of the {@code subcomponent} being registered. To register display data in the
* current namespace, such as from a base class implementation, use
* {@code super.populateDisplayData(builder)} instead.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

{@code include(subcomponent)} -> {@code builder.include(subcomponent)}
{@code super.populateDisplaydtaa(builder)} -> {@code subcomponent.populateDisplayData(builder)}

That way we're consistent with the example and suggestion.

@swegner
Copy link
Contributor Author

swegner commented May 2, 2016

I've addressed all feedback so far. Please take another look. @bjchambers

@bjchambers
Copy link
Contributor

LGTM

@asfgit asfgit closed this in 1262819 May 2, 2016
@swegner swegner deleted the classfordisplay branch May 11, 2016 17:51
@swegner
Copy link
Contributor Author

swegner commented May 16, 2016

Backport: GoogleCloudPlatform/DataflowJavaSDK#230

iemejia pushed a commit to iemejia/beam that referenced this pull request Jan 12, 2018
mareksimunek added a commit to mareksimunek/beam that referenced this pull request May 9, 2018
mareksimunek added a commit to mareksimunek/beam that referenced this pull request May 9, 2018
fixed tests

[euphoria-core] hints in getBasicOps are only on last operator

[euphoria-core] code style corrections

[euphoria-core] code style corrections 2
mareksimunek pushed a commit to mareksimunek/beam that referenced this pull request May 9, 2018
[euphoria-core] apache#259 Hints are not runtime specific.
dmvk pushed a commit to dmvk/beam that referenced this pull request May 15, 2018
dmvk pushed a commit to dmvk/beam that referenced this pull request May 15, 2018
fixed tests

[euphoria-core] hints in getBasicOps are only on last operator

[euphoria-core] code style corrections

[euphoria-core] code style corrections 2
mareksimunek added a commit to seznam/beam that referenced this pull request Jul 9, 2018
mareksimunek added a commit to seznam/beam that referenced this pull request Jul 9, 2018
fixed tests

[euphoria-core] hints in getBasicOps are only on last operator

[euphoria-core] code style corrections

[euphoria-core] code style corrections 2
dmvk pushed a commit to seznam/beam that referenced this pull request Aug 17, 2018
dmvk pushed a commit to seznam/beam that referenced this pull request Aug 17, 2018
fixed tests

[euphoria-core] hints in getBasicOps are only on last operator

[euphoria-core] code style corrections

[euphoria-core] code style corrections 2
dmvk pushed a commit to seznam/beam that referenced this pull request Oct 5, 2018
dmvk pushed a commit to seznam/beam that referenced this pull request Oct 5, 2018
fixed tests

[euphoria-core] hints in getBasicOps are only on last operator

[euphoria-core] code style corrections

[euphoria-core] code style corrections 2
damccorm added a commit that referenced this pull request Dec 9, 2022
…f-hosted runners (#23134)

* Updating build_playground_backend workflow (#167)

Co-authored-by: Elias Segundo <elias.segundo@luisrazo.local>

* Added master changes in build_playground_backend to avoid merge conflicts

* Reverted GO_VERSION and BEAM_VERSION to have the same as master

build_playground_backend

* Switching trigger to pull_request (#259)

* Switching to pull_request

* Removing ref from checkout

Co-authored-by: Elias Segundo Antonio <eliassegundo.segundo@gmail.com>
Co-authored-by: Elias Segundo <elias.segundo@luisrazo.local>
Co-authored-by: elink22 <103056145+elink22@users.noreply.github.com>
Co-authored-by: Danny McCormick <dannymccormick@google.com>
lostluck pushed a commit to lostluck/beam that referenced this pull request Dec 22, 2022
…f-hosted runners (apache#23134)

* Updating build_playground_backend workflow (apache#167)

Co-authored-by: Elias Segundo <elias.segundo@luisrazo.local>

* Added master changes in build_playground_backend to avoid merge conflicts

* Reverted GO_VERSION and BEAM_VERSION to have the same as master

build_playground_backend

* Switching trigger to pull_request (apache#259)

* Switching to pull_request

* Removing ref from checkout

Co-authored-by: Elias Segundo Antonio <eliassegundo.segundo@gmail.com>
Co-authored-by: Elias Segundo <elias.segundo@luisrazo.local>
Co-authored-by: elink22 <103056145+elink22@users.noreply.github.com>
Co-authored-by: Danny McCormick <dannymccormick@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants