Skip to content
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

Task/wg 193 add tup core components lib #190

Merged
merged 8 commits into from
Jan 8, 2024

Conversation

sophia-massie
Copy link
Contributor

@sophia-massie sophia-massie commented Jan 8, 2024

Overview:

PR Status:

  • Ready.
  • Work in Progress.
  • Hold.

Related Jira tickets:

Summary of Changes:

  • Added core-component dir from TUP-UI
  • Updated configs and packages needed for core-Components
  • Ignoring core-components tests in test script
  • Allow for implict any type as per the tsconfigs of TUP
  • Allow for js to be compiled
  • Added styles README from TUP for our reference

Testing Steps:

  1. Make sure you're using latest iron node by running nvm use lts/iron
  2. Then npm ci
  3. Then build and run dev
  4. Go to http://localhost:4200/ and make sure it displays
    "Main Menu
    Projects
    You have {x} projects."
  5. In the code base, go to src/pages/MainMenu.tsx change line 12 to (!isLoading) and make sure loading spinner appears.
  6. In the code base, go to src/pages/MainMenu.tsx change line 19 to (!error) to make sure message displays in red.

Notes:

- Ignoring core-components tests in npm run test
- Allow for implict any as per the tsconfigs of TUP
- Allow for js to be compiled
- Added styles README from TUP for our reference
@tjgrafft
Copy link
Contributor

tjgrafft commented Jan 8, 2024

Just a heads up, the screenshots for comparison aren't rendering for me. I think the links are broken?

@sophia-massie
Copy link
Contributor Author

Just a heads up, the screenshots for comparison aren't rendering for me. I think the links are broken?

Try refreshing - I took those instructions/screen shots out.

Copy link
Contributor

@tjgrafft tjgrafft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested everything locally and the Loading Spinner and Error Message appeared as expected! Great job! Having these common components to work with is gonna make life so much easier for us! So thanks for moving them over!

Wanted to get you and Nathan's thoughts on the following:

  • When doing the 'npm ci' command I got an output response of 8 vulnerabilities (6 moderate, 1 high, and 1 critical) Is this something in our control, that we can address?
  • When doing the 'npm run build' command I got an output response of several warning related to minifying the css. Should we make a sub-task to handle this later?

Copy link
Collaborator

@nathanfranklin nathanfranklin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome. LGTM 👍

@babel/traverse  <7.23.2
node_modules/@babel/traverse
semver  6.0.0 - 6.3.0 || 7.0.0 - 7.5.1
tough-cookie  <4.1.3
vite  3.0.2 - 3.2.6
word-wrap  <1.2.4
@sophia-massie sophia-massie merged commit 8674611 into master Jan 8, 2024
5 checks passed
@sophia-massie sophia-massie deleted the task/wg-193-Add-TUP-Core-Components-Lib branch January 8, 2024 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants