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

chore: add Phoenix CoreComponents, upgrade to Phoenix 1.7 #2136

Closed
wants to merge 2 commits into from

Conversation

bklebe
Copy link
Contributor

@bklebe bklebe commented Aug 2, 2024

Summary of changes

Asana Ticket: Import the set of base Phoenix.Components


General checks

  • Are the changes organized into self-contained commits with descriptive and well-formatted commit messages? This is a good practice that can facilitate easier reviews.
  • Testing. Do the changes include relevant passing updates to tests? This includes updating screenshots. Preferably tests are run locally to verify that there are no test failures created by these changes, before opening a PR.
  • Tech debt. Have you checked for tech debt you can address in the area you're working in? This can be a good time to address small issues, or create Asana tickets for larger issues.

New UI, or substantial UI changes

  • Cross-browser compatibility is less of an issue now that we're no longer supporting IE, but changes still need to work as expected in Safari, Chrome, and Firefox.
  • Are interactive elements accessible? This includes at minimum having relevant keyboard interactions and visible focus, but can also include verification with screen reader testing.
  • Other accessibility checks such as sufficient color constrast, or whether the layout holds up at 200% zoom level.

New endpoints, or non-trivial changes to current endpoints

  • Have we load-tested any new pages or internal API endpoints that will receive significant traffic? See load testing docs
  • If this change involves routes, does it work correctly with pertinent "unusual" routes such as the combined Green Line, Silver Line, Foxboro commuter rail, and single-direction bus routes like the 170?

@bklebe bklebe force-pushed the beatrix/push/kxrlwxznkvmy branch 4 times, most recently from b66a808 to 93aca61 Compare August 8, 2024 14:48
@bklebe bklebe force-pushed the beatrix/push/kxrlwxznkvmy branch from 93aca61 to 4a704dd Compare August 20, 2024 14:17
@bklebe bklebe closed this Aug 22, 2024
@bklebe bklebe mentioned this pull request Aug 22, 2024
8 tasks
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.

1 participant