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

getMetadata refactor #53

Closed
wants to merge 1 commit into from
Closed

getMetadata refactor #53

wants to merge 1 commit into from

Conversation

freeformz
Copy link
Contributor

This was part of ffz/Optimize. I'm very sure this wasn't part of the
problem.

This dedents most of the logic & removes (what is in my opinion) the
unnecessary bool return (it's a guard on the length of the bytes).

Dedenting the majority of the logic in a function a go best practice.

@freeformz
Copy link
Contributor Author

I'm still wondering what the actual problem was, but I'm confident this refactor wasn't part of it.

In order to minimize the number of possible changes I'd like to propose them one at a time, ensure they're deployed, and not causing errors before moving onto the next one.

Thoughts?

This was part of ffz/Optimize. I'm very sure this wasn't part of the
problem.

This dedents most of the logic & removes (what is in my opinion) the
unnecessary bool return (it's a guard on the length of the bytes).

Dedenting the majority of the logic in a function a go best practice.
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

1 participant