-
Notifications
You must be signed in to change notification settings - Fork 324
Development
: Remove unused localVCenabled value from client
#10478
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
Development
: Remove unused localVCenabled value from client
#10478
Conversation
WalkthroughThis pull request removes the Changes
Possibly related PRs
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
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.
see Github errors
src/test/javascript/spec/component/account/user-settings-container.component.spec.ts
Outdated
Show resolved
Hide resolved
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/test/javascript/spec/component/account/user-settings-container.component.spec.ts (1)
42-48
: Align spy verifications with coding guidelinesThe test looks good overall, but there are a couple of improvements that would better align with the coding guidelines:
- For spy verification on line 45, use the more specific
toHaveBeenCalledOnce()
instead of the generictoHaveBeenCalled()
- For boolean expectation on line 47, use
toBeFalse()
instead oftoEqual(false)
as per the guidelinesit('should initialize with loaded user', () => { const getAuthenticationSpy = jest.spyOn(accountService, 'getAuthenticationState'); fixture.detectChanges(); - expect(getAuthenticationSpy).toHaveBeenCalled(); + expect(getAuthenticationSpy).toHaveBeenCalledOnce(); expect(comp.currentUser?.id).toEqual(99); - expect(comp.isAtLeastTutor).toEqual(false); + expect(comp.isAtLeastTutor).toBeFalse(); });
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
src/test/javascript/spec/component/account/user-settings-container.component.spec.ts
(1 hunks)src/test/javascript/spec/component/exercises/shared/exercise-scores/exercise-scores.component.spec.ts
(0 hunks)
💤 Files with no reviewable changes (1)
- src/test/javascript/spec/component/exercises/shared/exercise-scores/exercise-scores.component.spec.ts
🧰 Additional context used
📓 Path-based instructions (1)
`src/test/javascript/spec/**/*.ts`: jest: true; mock: NgMocks; bad_practices: avoid_full_module_import; perf_improvements: mock_irrelevant_deps; service_testing: mock_http_for_logi...
src/test/javascript/spec/**/*.ts
: jest: true; mock: NgMocks; bad_practices: avoid_full_module_import; perf_improvements: mock_irrelevant_deps; service_testing: mock_http_for_logic; no_schema: avoid_NO_ERRORS_SCHEMA; expectation_specificity: true; solutions: {boolean: toBeTrue/False, reference: toBe, existence: toBeNull/NotNull, undefined: toBeUndefined, class_obj: toContainEntries/toEqual, spy_calls: {not_called: not.toHaveBeenCalled, once: toHaveBeenCalledOnce, with_value: toHaveBeenCalledWith|toHaveBeenCalledExactlyOnceWith}}
src/test/javascript/spec/component/account/user-settings-container.component.spec.ts
⏰ Context from checks skipped due to timeout of 90000ms (7)
- GitHub Check: Build and Push Docker Image / Build Docker Image for ls1intum/artemis
- GitHub Check: Build and Push Docker Image / Build Docker Image for ls1intum/artemis
- GitHub Check: Build .war artifact
- GitHub Check: client-tests-selected
- GitHub Check: client-tests
- GitHub Check: server-tests
- GitHub Check: Analyse
🔇 Additional comments (2)
src/test/javascript/spec/component/account/user-settings-container.component.spec.ts (2)
31-31
: LGTM - Using MockAccountService as requestedThe changes properly implement the previous review comment by using MockAccountService instead of a manual mock.
25-25
: Simplification of imports looks goodThe component imports have been simplified to only include what's necessary, which improves maintainability.
There hasn't been any activity on this pull request recently. Therefore, this pull request has been automatically marked as stale and will be closed if no further activity occurs within seven days. Thank you for your contributions. |
528b6fc
to
5dfa308
Compare
End-to-End (E2E) Test Results Summary
|
End-to-End (E2E) Test Results Summary
|
There hasn't been any activity on this pull request recently. Therefore, this pull request has been automatically marked as stale and will be closed if no further activity occurs within seven days. Thank you for your contributions. |
The repeated necessary effort of resolving the merge conflicts introduced by the client code refactorings leads me to close this PR |
Checklist
General
Motivation and Context
In the client are still remnants of the gitlab setup.
As the localVCenabled flag is always true now, the client code depending on it can be removed.
Description
Steps for Testing
Testserver States
You can manage test servers using Helios. Check environment statuses in the environment list. To deploy to a test server, go to the CI/CD page, find your PR or branch, and trigger the deployment.
Review Progress
Code Review
Manual Tests
Test Coverage
Screenshots
no UI change
Summary by CodeRabbit