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.

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

fix configMapSelector typo #161

Merged
merged 1 commit into from
Oct 3, 2023
Merged

Conversation

isaaguilar
Copy link
Collaborator

fixes from configMapSeclector to configMapSelector in the crd.

fixes from `configMapSeclector` to `configMapSelector` in the crd.
@isaaguilar
Copy link
Collaborator Author

Fixes #153

@isaaguilar isaaguilar merged commit 791b4b5 into master Oct 3, 2023
3 checks passed
@davhdavh
Copy link

davhdavh commented Oct 6, 2023

Why did you keep the misspelled one? the change to the go-code clearly shows it could never parse it since it was using the right name in go

@isaaguilar
Copy link
Collaborator Author

Both the misspelling and correct spelling works for me. When unmarshalling, the un-marshaller correctly populates the variables from by reading the associated tags (json:"configMapSelector,omitempty" & json:"configMapSeclector,omitempty").

I didn't fix anything here except a new variable name that preserves the old tag in case it was working a certain way for someone else.

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.

None yet

2 participants