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

BHBC-785 #152

Merged
merged 14 commits into from
Mar 22, 2021
Merged

BHBC-785 #152

merged 14 commits into from
Mar 22, 2021

Conversation

cgarrettjones
Copy link
Contributor

@cgarrettjones cgarrettjones commented Mar 22, 2021

BHBC-785
Summary First pass model the solution for dealing with attachments added to BioHub projects in the first release
Type Story Story
Status In Progress
Points N/A
Labels -

Overview

Links to jira tickets

  • BHBC-785

This PR contains the following changes

  • addition of project_attachment table
  • addition of system_constant table
  • some name fixing for table and ids around IUCN

This PR contains the following types of changes

  • New feature (change which adds functionality)
  • Enhancement (improvements to existing functionality)
  • Bug fix (change which fixes an issue)
  • Misc cleanup / Refactoring / Documentation
  • Version change

Checklist

A list of items that are good to consider when making any changes.

Note: this list is not exhaustive, and not all items are always applicable.

General

  • I have performed a self-review of my own code

Code

  • New files/classes/functions have appropriately descriptive names and comment blocks to describe their use/behaviour
  • I have avoided duplicating code when possible, moving re-usable pieces into functions
  • I have avoided hard-coding values where possible and moved any re-usable constants to a constants file
  • My code is as flat as possible (avoids deeply nested if/else blocks, promise chains, etc)
  • My code changes account for null/undefined values and handle errors appropriately
  • My code uses types/interfaces to help describe values/parameters/etc, help ensure type safety, and improve readability

Style

  • My code follows the established style conventions
  • My code uses native material-ui components/icons/conventions when possible

Documentation

  • I have commented my code sufficiently, such that an unfamiliar developer could understand my code
  • I have added/updated README's and related documentation, as needed

Tests

  • I have added/updated unit tests for any code I've added/updated
  • I have added/updated the Postman requests/tests to account for any API endpoints I've added/updated

Linting/Formatting

  • I have run the linter and fixed any issues, as needed
    See the lint commands in package.json
  • I have run the formatter and fixed any issues, as needed
    See the format commands in package.json

SonarCloud

  • I have addressed all SonarCloud Bugs, Vulnerabilities, Security Hotspots, and Code Smells

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Screenshots

Please add any relevant UI screenshots, if applicable.

@github-actions
Copy link

Knock Knock! 🔍

Just thought I'd let you know that your PR title and story title look quite different. PR titles that closely resemble the story title make it easier for reviewers to understand the context of the PR.

An easy-to-understand PR title a day makes the reviewer review away! 😛⚡️
Story Title First pass model the solution for dealing with attachments added to BioHub projects in the first release
PR Title BHBC-785

Check out this guide to learn more about PR best-practices.

@codecov
Copy link

codecov bot commented Mar 22, 2021

Codecov Report

Merging #152 (18a9859) into dev (b8f7bca) will not change coverage.
The diff coverage is 44.44%.

Impacted file tree graph

@@           Coverage Diff           @@
##              dev     #152   +/-   ##
=======================================
  Coverage   44.52%   44.52%           
=======================================
  Files         102      102           
  Lines        2010     2010           
  Branches      456      456           
=======================================
  Hits          895      895           
  Misses       1040     1040           
  Partials       75       75           
Impacted Files Coverage Δ
api/src/paths/codes.ts 0.00% <ø> (ø)
api/src/paths/project.ts 0.00% <0.00%> (ø)
api/src/queries/code-queries.ts 0.00% <0.00%> (ø)
app/src/features/projects/CreateProjectPage.tsx 65.11% <0.00%> (ø)
api/src/queries/project-queries.ts 77.35% <100.00%> (ø)
...c/features/projects/components/ProjectIUCNForm.tsx 64.28% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b8f7bca...18a9859. Read the comment docs.

sdevalapurkar
sdevalapurkar previously approved these changes Mar 22, 2021
Copy link
Contributor

@sdevalapurkar sdevalapurkar left a comment

Choose a reason for hiding this comment

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

LGTM, haven't run it locally - but I think it looks good (specifically based on the iucn table updates)

Copy link
Contributor

@anissa-agahchen anissa-agahchen left a comment

Choose a reason for hiding this comment

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

Looks good.

@NickPhura NickPhura dismissed stale reviews from anissa-agahchen and sdevalapurkar via ff3f387 March 22, 2021 20:48
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@anissa-agahchen anissa-agahchen merged commit f069c1e into dev Mar 22, 2021
@anissa-agahchen anissa-agahchen deleted the BHBC-785 branch March 22, 2021 21:07
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.

4 participants