Skip to content
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.

Manual update to help Long Term Maintenance #359

Merged
merged 21 commits into from
Nov 24, 2021

Conversation

22antonio
Copy link
Contributor

@22antonio 22antonio commented Nov 10, 2021

Changes

  1. Updated SpecReporter syntax
  2. Update Docker node version from 10 to 12
  3. Update Angular/Angular dependencies
  4. Updated npm packages
  5. Added EsLint as new linter

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

@22antonio 22antonio added the dependencies Pull requests that update a dependency file label Nov 10, 2021
@22antonio 22antonio marked this pull request as ready for review November 17, 2021 23:40
@22antonio 22antonio requested a review from mwallert as a code owner November 17, 2021 23:40
@22antonio 22antonio requested review from a team, aneshamoore and gyuhunlee and removed request for a team November 17, 2021 23:40
@22antonio
Copy link
Contributor Author

commit 62dee66 should be chore(deps)... not chore(docker)... .

@22antonio 22antonio changed the title Am 340 long term maintenance Manual update to help Long Term Maintenance Nov 18, 2021
@mwallert
Copy link
Contributor

@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.

@michaelachrisco
Copy link
Contributor

@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.

@michaelachrisco
Copy link
Contributor

I cant remove you 😆 So Ill just add myself for now. And get to that CODEOWNERS/dev->main up to date branches.

@michaelachrisco michaelachrisco self-requested a review November 18, 2021 21:32
@michaelachrisco
Copy link
Contributor

commit 62dee66 should be chore(deps)... not chore(docker)... .

Its all good. Next time, I would suggest using git rebase to change the git commit messages. No worries here.

@michaelachrisco
Copy link
Contributor

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!

Copy link
Contributor

@michaelachrisco michaelachrisco left a 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 22antonio requested a review from AramayisO as a code owner November 23, 2021 18:41
@22antonio
Copy link
Contributor Author

I pushed some updates to fix the incompatibility issues I was having with the newer version of node and angular.
I was able to:

  • Manually add users and agents.
  • Directories would update as they should.
  • Login as other users not just seeded.
  • Password checking worked.

Login screenshot you requested:
Screen Shot 2021-11-23

@michaelachrisco
Copy link
Contributor

@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.

Copy link
Contributor

@michaelachrisco michaelachrisco left a 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.

Copy link
Contributor

@AramayisO AramayisO left a 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?

src/app/app.component.spec.ts Show resolved Hide resolved
@@ -3,7 +3,7 @@ jobs:
test:
working_directory: ~/boilerplate-client-angular
docker:
- image: 'circleci/node:10-browsers'
- image: 'circleci/node:14-browsers'
Copy link
Contributor

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?

Copy link
Contributor Author

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 👍

Comment on lines +1 to +2
import * as packageInfo from '../../package.json';
const { name, version } = packageInfo;
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor Author

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

Copy link
Contributor

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.

src/environments/environment.ts Show resolved Hide resolved
@22antonio
Copy link
Contributor Author

@michaelachrisco

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.

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?

@michaelachrisco
Copy link
Contributor

michaelachrisco commented Nov 24, 2021

@michaelachrisco

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.

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.

@22antonio
Copy link
Contributor Author

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

@22antonio 22antonio merged commit 1b2eafc into development Nov 24, 2021
@22antonio 22antonio deleted the am-340-long-term-maintenance branch November 24, 2021 20:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants