Skip to content
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.

Sign up for GitHub

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

Jump to bottom

⚠️ Handler: Remove MapObject type and use client.Object directly #1207

Merged
merged 1 commit into from
Oct 2, 2020
Merged

⚠️ Handler: Remove MapObject type and use client.Object directly #1207

merged 1 commit into from
Oct 2, 2020

Commits on Oct 2, 2020

  1. ⚠️ Handler: Remove MapObject type and use client.Object directly 

    We updated the handlers MapObject type to not include a metav1.Object
and a runtime.Object representation of the same object but instead a
client.Object, which is a union of the two above.

The only reason for the MapObject type to exist in the first place
though was to hold these two fields. Now that there is only the
client.Object left, we can use that directly and get rid of the
MapObject type.
    @alvaroaleman
    alvaroaleman committed Oct 2, 2020
    Configuration menu
    Copy the full SHA
    f35d811 View commit details
    Browse the repository at this point in the history