-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[BEAM-231] Remove ClassForDisplay helper type #259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
R: @bjchambers |
| super.populateDisplayData(builder); | ||
|
|
||
| Combine.populateDisplayData(builder, fn, fnClass); | ||
| Combine.populateDisplayData(builder, fn, fnDisplayData); |
There was a problem hiding this comment.
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(...)?
There was a problem hiding this comment.
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.
|
In |
|
I've addressed all feedback so far. Please take another look. @bjchambers |
|
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 |
There was a problem hiding this comment.
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 ...
|
Minor wording comments, then LGTM |
c733ae2 to
9bbc143
Compare
|
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. |
There was a problem hiding this comment.
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.
|
I've addressed all feedback so far. Please take another look. @bjchambers |
|
LGTM |
|
Backport: GoogleCloudPlatform/DataflowJavaSDK#230 |
…ribe OutputDataset
fixed tests [euphoria-core] hints in getBasicOps are only on last operator [euphoria-core] code style corrections [euphoria-core] code style corrections 2
[euphoria-core] apache#259 Hints are not runtime specific.
…ribe OutputDataset
fixed tests [euphoria-core] hints in getBasicOps are only on last operator [euphoria-core] code style corrections [euphoria-core] code style corrections 2
…ribe OutputDataset
fixed tests [euphoria-core] hints in getBasicOps are only on last operator [euphoria-core] code style corrections [euphoria-core] code style corrections 2
…ribe OutputDataset
fixed tests [euphoria-core] hints in getBasicOps are only on last operator [euphoria-core] code style corrections [euphoria-core] code style corrections 2
…ribe OutputDataset
fixed tests [euphoria-core] hints in getBasicOps are only on last operator [euphoria-core] code style corrections [euphoria-core] code style corrections 2
…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>
…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>
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
[BEAM-<Jira issue #>] Description of pull requestmvn clean verify. (Even better, enableTravis-CI on your fork and ensure the whole test matrix passes).
<Jira issue #>in the title with the actual Jira issuenumber, if there is one.
Individual Contributor License Agreement.