-
Notifications
You must be signed in to change notification settings - Fork 0
Manual update to help Long Term Maintenance #359
Conversation
This reverts commit 90101e4.
commit 62dee66 should be chore(deps)... not chore(docker)... . |
@michaelachrisco It looks like development and main are out of sync for codeowners. I'm not sure I will have time to get to this PR before EOD and I'm out next week. |
@mwallert Thanks for letting me know. @22antonio Lets go over this on Monday. Looks like we may need to prune this real quick. Ill remove @mwallert from the PR and assign myself in place. |
I cant remove you 😆 So Ill just add myself for now. And get to that CODEOWNERS/dev->main up to date branches. |
Its all good. Next time, I would suggest using |
As we discussed, @22antonio will be taking a look at the UI and finding out if the features are working. He will also include a screenshot of a logged in session just to make sure. After that, this should be good! |
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.
As we discussed, @22antonio will be taking a look at the UI and finding out if the features are working. He will also include a screenshot of a logged in session just to make sure. After that, this should be good!
@22antonio Let me know when this is finished and we can take a quick second look. Thanks!
@22antonio Awesome job here!! Looks great. Can you do me a favor and update the README with the correct versions of the Angular CLI? https://github.com/Shift3/boilerplate-client-angular/blob/main/README.md Looks like the readme references v9. |
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.
Pulled down the repo, looks like everything is working to what I can see. Awesome job here @22antonio ! Non-blocker but I if you could update the README with the correct versions that would help out as well.
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.
Great job on this PR. Good to see the project updated to use the latest versions of the Angular CLI and updated version of Node.
One question regarding the CircleCI config.yml
. I believe the newer version of Angular CLI specifically requires Node version 14.15. The CI config specifies to use the circleci/node:14-browsers
image. Is it possible to restrict it to version 14.15 so it doesn't use a newer version of Node 14 and cause the Angular CLI to throw an error?
.circleci/config.yml
Outdated
@@ -3,7 +3,7 @@ jobs: | |||
test: | |||
working_directory: ~/boilerplate-client-angular | |||
docker: | |||
- image: 'circleci/node:10-browsers' | |||
- image: 'circleci/node:14-browsers' |
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.
Nice! We were pretty behind on the node version.
One question, since the new version of Angular CLI requires Node v14.15, can we restrict the image here to 14.15 so it doesn't pull a newer version of node 14.* and cause CI to fail?
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.
Thank you for the suggestion. I just pushed up a change to enforce the specific version. It looks like it works 👍
import * as packageInfo from '../../package.json'; | ||
const { name, version } = packageInfo; |
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.
Not a blocker, but is there a reason for importing everything from package.json
instead of deestructuring just what we need?
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.
I was getting an error when trying to access package variables that way. I don't recall the error though I'll have to find it for you.
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.
I believe this is no longer the way to access package.json
variables. It has been deprecated
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.
Interesting. I'll have to look into it as well because we are still doing it the old way in the React boilerplate.
I just updated the README with the correct version of Angular CLI. While I was looking at it I noticed that it still has a section talking about Protractor. Since Protractors been deprecated how should I handle that part of the README? |
Are we still using it within our testing suite? Unless its been completely stripped out, lets keep that section for now. If not, lets remove. |
I left it since we don't have a proper replacement yet. In this case I think it should get removed when we complete #365 |
Changes
Purpose
This manual update should help with some of the maintenance of the project.
Learning
Working example of jasmine-spec-reporter
Protractor is deprecated
TsLint is deprecated, EsLint is the replacement
ESLint v5 is not supported by angular right now
Fixes #340