-
Notifications
You must be signed in to change notification settings - Fork 437
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
add import of missing Angular interfaces (squashed version) #3048
Conversation
Should I open an issue for the adoption of an additional lint rule as suggested by @ybnd in #2870 (comment) ? |
One test is failing, but it is not related to the proposed changes:
|
@saschaszott : We've had random failures from that "Edit Item" e2e test. It's not specific to this PR. I've restarted the tests, as usually it passes after rerunning the tests. |
Thanks @saschaszott. I tested this by doing an item submission and searching with the sandbox.dspace.org instance as a backend. All working fine. Passing all tests too. Happy to merge this as it's
1 APPROVAL
I'm curious what the issue is here, though? If these interfaces were missing and everything was already working, what problem is this solving? 😄 |
https://www.reddit.com/r/Angular2/comments/ge3evp/comment/fpmzpah/ |
@alanorth everything will still work if we don't implement those interfaces, but this way the intent is a lot more clear and it can serve as a sort of spell-check too https://v17.angular.io/guide/styleguide#implement-lifecycle-hook-interfaces
|
@alanorth , to enforce the import of Angular lifecycle interfaces a lint rule should be added as suggested by @ybnd in #2870 (comment) |
Awesome, thanks for the explanations. This sounds reasonable to me, but I will let someone familiar with Angular give the final approval. |
@ybnd : Since you seem to agree with this direction... I wanted to see if you're interested in reviewing this? If you approve of this & have tested it yourself, then I think this can be merged. I do agree with @alanorth that'd it'd be nice to have another "Angular expert" at a different institution from @saschaszott to approve this. But, in my opinion, you'd qualify for that, @ybnd if you have time :) In general, I agree with the direction here (and thank you to @saschaszott !). I just have not had time to get to myself yet (as I have a lot on my plate). So, it's only waiting for someone to have time to give it a code review. |
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.
The changes that you've made so far are all good, but it looks that there's a few more files that should be updated.
Can you add "@angular-eslint/use-lifecycle-interface": "error"
to .eslintrc.json
and run yarn lint --fix
?
This should fix the remaining problems and cover any upcoming ones as well.
@ybnd , this PR is ready for review. |
Merging with one approval. Looks good to me too. Thanks again @saschaszott ! |
Successfully created backport PR for |
Description
This PR is a replacement of #2870 where all commits were squashed into one commit as suggested by @alanorth .
It is synced with the latest changes in
main
branch.