You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the right side of this issue, create a new branch
Check the right side of the GitHub UI
Use the commands provided to switch to that branch before you begin working
The commands will pop up once you make the branch
IMPORTANT
We are using Yarn. NEVER npm install, always use Yarn
BEFORE you commit, use git add <names of files>. ONLY add files you modified, including the yarn.lock if you added new modules
BEFORE you commit, use git status. Ensure files you changed are in green, irrelevant files are in red
Make sure you always push to your new branch, never push to main
See the bottom of this doc for resources on Git if you are lost, and feel free to reach out to Nate and Jessie at any time!
NOTE:
We are using PostgreSQL, not just SQL. Be sure to include Postgres when searching for documentation.
For time/datetime types, see this documentation: link
Task
Implement the invoices table (found in the DB model linked below)
A template has been created for you on this website
This template will let you implement and test your invoices table
When done on the DB Fiddle, create a new file called invoices.sql in /lpa/server/db/schema/
Do this locally in VS code or your files, do not do this on the GitHub website
The GitHub desktop client is not recommended, it is a good skill to learn the command line!
Put the create statement for invoices table in that file. DO NOT put any of the other template SQL or comments
Commit and push these changes to GitHub
Create a PR describing the changes you made
Pre-submit checklist
The invoices table on DB fiddle runs without errors
The provided insert statements run
I have written more insert statements to test unique constraints and defaults
Changes are committed to a new branch for this issue (don't commit to MAIN!!)
Welcome to your first sprint task!
Setup
IMPORTANT
npm install
, always use Yarngit add <names of files>
. ONLY add files you modified, including the yarn.lock if you added new modulesgit status
. Ensure files you changed are in green, irrelevant files are in redNOTE:
We are using PostgreSQL, not just SQL. Be sure to include Postgres when searching for documentation.
For time/datetime types, see this documentation: link
Task
Pre-submit checklist
Now, create the PR!
Please complete before November 30th
Resources
The text was updated successfully, but these errors were encountered: