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

bugfix/KBDEV-1254 New Records of Abstract Classes Unnecessarily Required Admin Permission #93

Merged

Conversation

bnguyen-bcgsc
Copy link
Contributor

  • Fix bug in main view where new records of abstract classes (e.g.: ontology, relationship) required admin permission
  • Fix rowData typos for ag grid calls
  • Code lint

- Fix bug in main view where new records of abstract classes (e.g.: ontology, relationship) required admin permission
- Fix rowData typos for ag grid calls
- Code lint
@bnguyen-bcgsc bnguyen-bcgsc added the bug Something isn't working label Sep 17, 2024
@bnguyen-bcgsc bnguyen-bcgsc self-assigned this Sep 17, 2024

This comment has been minimized.

This comment has been minimized.

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.76%. Comparing base (8179a92) to head (2f205e7).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #93   +/-   ##
========================================
  Coverage    56.76%   56.76%           
========================================
  Files          102      102           
  Lines         3874     3874           
  Branches      1310     1310           
========================================
  Hits          2199     2199           
  Misses        1663     1663           
  Partials        12       12           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mathieulemieux
Copy link
Member

I don't understand why we need a client code change while ticket describes a very recent behavior. Any idea @bnguyen-bcgsc or @elewis2 ?

@bnguyen-bcgsc
Copy link
Contributor Author

I don't understand why we need a client code change while ticket describes a very recent behavior. Any idea @bnguyen-bcgsc or @elewis2 ?

@mathieulemieux we suspect that it worked initially because they had not hard-refresh the client when the new version was released and the change was made using 4.2.3. After examining the behaviour and recreating the issue, line 110 of MainView was determined to be the cause of the problem

@mathieulemieux
Copy link
Member

@bnguyen-bcgsc, was the issue reported on prod? because last update was more than 2y ago...

@mathieulemieux
Copy link
Member

Maybe the deployed version was still 4.2.3 though... I think we documented that issue before, so if it's the case, then it's start to make sense.

@bnguyen-bcgsc
Copy link
Contributor Author

@bnguyen-bcgsc, was the issue reported on prod? because last update was more than 2y ago...

I don't believe so since the change that caused the issue was added in just 6 months ago

@bnguyen-bcgsc bnguyen-bcgsc merged commit 3022954 into develop Sep 17, 2024
3 checks passed
Copy link

Unit Test Results

    1 files  ±0    39 suites  ±0   1m 37s ⏱️ -1s
160 tests ±0  159 ✔️ ±0  1 💤 ±0  0 ❌ ±0 
156 runs  ±0  155 ✔️ ±0  1 💤 ±0  0 ❌ ±0 

Results for commit 3022954. ± Comparison against base commit 8179a92.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants