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

Use resource_type_id instead of types.resourceTypeGeneral when filtering #1036

Merged
merged 7 commits into from
Nov 3, 2023

Conversation

bklaing2
Copy link
Member

Purpose

Use resource_type_id instead of types.resourceTypeGeneral when filtering

Approach

Open Questions and Pre-Merge TODOs

Learning

Types of changes

  • Bug fix (non-breaking change which fixes an issue)

  • New feature (non-breaking change which adds functionality)

  • Breaking change (fix or feature that would cause existing functionality to change)

Reviewer, please remember our guidelines:

  • Be humble in the language and feedback you give, ask don't tell.
  • Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
  • Offer suggestions on how to improve code e.g. simplification or expanding clarity.
  • Ensure you give reasons for the changes you are proposing.

@bklaing2 bklaing2 requested a review from jrhoads October 30, 2023 18:06
@bklaing2 bklaing2 self-assigned this Oct 30, 2023
def handleResourceType(types)
if types["resourceType"] == "Project" && (types["resourceTypeGeneral"] == "Text" || types["resourceTypeGeneral"] == "Other")
def handle_resource_type(types)
if !types.nil? && types["resourceType"] == "Project" && (types["resourceTypeGeneral"] == "Text" || types["resourceTypeGeneral"] == "Other")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This if statement could read a tiny bit better if you used types.present? instead of !types.nil?. I appreciate that this comment could be considered a nit.

@bklaing2 bklaing2 merged commit d365ee8 into master Nov 3, 2023
13 checks passed
@bklaing2 bklaing2 deleted the fair-work-feature-5 branch November 3, 2023 15:28
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.

3 participants