-
Notifications
You must be signed in to change notification settings - Fork 20
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
Business Search to tabbed interface #90
Conversation
Codecov Report
@@ Coverage Diff @@
## main #90 +/- ##
==========================================
+ Coverage 70.27% 70.87% +0.60%
==========================================
Files 52 54 +2
Lines 1497 1631 +134
Branches 168 193 +25
==========================================
+ Hits 1052 1156 +104
- Misses 415 437 +22
- Partials 30 38 +8
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Just has a test failure and can you add a postman test + example for the endpoint?
@@ -119,6 +119,10 @@ class _Config(): # pylint: disable=too-few-public-methods | |||
except (TypeError, ValueError): | |||
JWT_OIDC_JWKS_CACHE_TIMEOUT = 300 | |||
|
|||
JWT_OIDC_USERNAME = os.getenv('JWT_OIDC_USERNAME', 'username') | |||
JWT_OIDC_FIRSTNAME = os.getenv('JWT_OIDC_FIRSTNAME', 'firstname') | |||
JWT_OIDC_LASTNAME = os.getenv('JWT_OIDC_LASTNAME', 'lastname') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what are these used for? Were they left in by mistake?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, This is the reason why user details were not getting saved in the db
|
||
const { search } = useSearch() | ||
|
||
const totalResultsLength = computed(() => search.results?.length || 0 ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fyi this will actually be the wrong value if the number of results is greater than the rows specified. The total will be here: search.searchResults.total_rows
(this is an existing bug)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh but what is the expected behavior in this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well I would have it show the full total since we'll be adding paging in
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But I guess that can wait until we implement paging on the front end
Test is fixed. I will add postman test in another PR |
Issue #: /bcgov/entity#12641
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the PPR license (Apache 2.0).