Skip to content
This repository has been archived by the owner on Jan 19, 2023. It is now read-only.

Reconciles unmarshal and base code differences #2669

Merged
merged 3 commits into from
Jul 23, 2021

Conversation

liamrathke
Copy link
Contributor

What this PR does / why we need it:

Currently, complex resource viewer graphs sent to Octant via a TypeScript plugin cannot be displayed, as Octant's unmarshal.go is unaware of what to do with certain resource viewer components. This PR updates unmarshal.go to handle all current component type constants handled in base.go, and reorders the content of both files alphabetically.

Kudos to @mklanjsek for debugging and helping me find the solution!

Testing steps:

To test this example, we'll use a sample TypeScript plugin that displays data in an Octant resource viewer

  1. Follow the installation instructions in the repo to install the plugin
  2. Run Octant off this branch, verify that all custom resource viewer graphs appear correctly

Release note:

Fixes issues preventing complex custom resource viewer graphs from being displayed in TypeScript-based plugins
Improves component infrastructure 

Prevents some errors when attempting to unmarshal components

Signed-off-by: Liam Rathke <[email protected]>
Signed-off-by: Liam Rathke <[email protected]>
@wwitzel3
Copy link
Contributor

Please add a changelog entry for this.

@wwitzel3
Copy link
Contributor

Sorry, for reference, instructions are here: https://github.com/vmware-tanzu/octant/blob/master/CONTRIBUTING.md#changelog

Signed-off-by: Liam Rathke <[email protected]>
pkg/view/component/unmarshal.go Outdated Show resolved Hide resolved
pkg/view/component/unmarshal.go Outdated Show resolved Hide resolved
pkg/view/component/unmarshal.go Outdated Show resolved Hide resolved
pkg/view/component/unmarshal.go Outdated Show resolved Hide resolved
pkg/view/component/unmarshal.go Outdated Show resolved Hide resolved
@GuessWhoSamFoo GuessWhoSamFoo merged commit 86da9bf into vmware-archive:master Jul 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants