-
Notifications
You must be signed in to change notification settings - Fork 32
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
Website architecture documentation #1199
Conversation
Signed-off-by: Peter Nied <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1199 +/- ##
=========================================
Coverage 80.39% 80.39%
Complexity 3094 3094
=========================================
Files 424 424
Lines 15742 15742
Branches 1066 1066
=========================================
Hits 12655 12655
Misses 2435 2435
Partials 652 652
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
LGTM! Added some top level questions I had while reading
*Local Dev* | ||
|
||
Next.js comes with a [dev webserver](https://nextjs.org/docs/app/api-reference/cli/next#next-dev-options) that runs all pages as part of a sever-side website. While this is slightly different experience from the static workflow writing code and seeing an update to the UX occurs in sub-second time frame - perfect for quickly iterating on layout and routing logic. |
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.
What would the testing cycle look like then to see a change on the UI locally when developing? In the past when working with React it has been nice to make a change and see the UI get updated rapidly
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.
💯 We are going to use npm run dev
to spin up a local webserver that dynamically updates, its v. fast
*Linting* | ||
|
||
Linters will be enforced for best practice management and code styling. All website components will follow these tooling that are available through NPM. Next.js has [default conventions](https://nextjs.org/docs/app/api-reference/config/eslint) for both eslint and prettier and we will enable them in our CI workflows. |
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.
Will this linting be in-line with the linting our CDK uses?
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.
We will keep using eslist. I am adding Prettier
, this won't impact the npm run dev
mode, build will check for style when files are imported. When these go in, or even later, we can tweak this setting as we come up with strong opinions on the TS style.
Description
Website architecture documentation
Issues Resolved
Testing
Prototype in progress in https://github.com/peternied/opensearch-migrations/tree/frontend-proto
Check List
New functionality includes testingPublic documentation issue/PR created, if applicable.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.