-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[BUG]: Is the linter, Check Angular Services Index Required #19462
Comments
Hi @seanlip, It seems like you're asking for a way to automatically add a newly created Angular Injectable to the Files changed:
|
@retrogtx We are not expecting to add any automation here, instead we are trying to understand why we need this check and whether it is still needed, if not we can remove it! @srijanreddy98 Do you know why we need this check and when can this be removed? |
my bad, noob behaviour from my side :-/ |
thanks will look into it! |
Out of issue question: May I know for running the frontend test cases what dependencies I will have to install? I'm new here please guide me!! |
It should be safe to remove the check but it is not yet safe to remove the angular-services index file. They have a unit test presence with importAllAngularServices and a runtime presence in Oppia root (where it is only present to import a predefined set of services. |
Describe the bug
When I create an angular injectable, say
ModeratorAuthGuard
, the linter will complain when I don't add it to the angular-services.index.ts file here:oppia/scripts/linters/js_ts_linter.py
Lines 381 to 431 in a0c1a6b
URL of the page where the issue is observed.
N/A
Steps To Reproduce
N/A
Expected Behavior
Is this lint check required?
Screenshots/Videos
No response
What device are you using?
Desktop
Operating System
Windows
What browsers are you seeing the problem on?
No response
Browser version
No response
Additional context
No response
Tips for developers
Before tackling the bug, please use
git bisect
(see https://git-scm.com/docs/git-bisect) to investigate which PR caused it. If the issue occurred before commit c7db0fe, the most effective approach is to utilize the Python setup for conducting agit bisect
(You only need to go back as far as commit https://github.com/oppia/oppia/commits/9a334e9). If you need to perform agit bisect
for any commit beyond that commit, the Docker setup will be suitable. If you find the PR, leave a comment on this issue pointing to it, or just say that it happened before commit 9a334e9 if you could reproduce it there. This will help us fix the issue by reverting the faulty PR.Also, if this is your first issue, please make sure to follow https://github.com/oppia/oppia/wiki/Contributing-code-to-Oppia#choosing-a-good-first-issue and https://github.com/oppia/oppia/wiki/Contributing-code-to-Oppia#setting-things-up before claiming it. Thanks!
The text was updated successfully, but these errors were encountered: