-
Notifications
You must be signed in to change notification settings - Fork 5
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
Bug Fix for Transaction Read/Write Error #401
Changes from all commits
371b22d
b4a479e
1ff3abd
70f48db
1fae7f3
ceeff67
aa4ec62
10286fb
f6ad1e1
0880cb4
c91671e
3ea1c89
d5195ea
c8afdf9
d882ebb
e71a921
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -479,7 +479,6 @@ async function seed(): Promise<void> { | |
}); | ||
const MERCH_ITEM_1_PHOTO_1 = MerchFactory.fakePhoto({ | ||
merchItem: MERCH_ITEM_1, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: maybe add these uploadedPhoto links back in for seeding data purposes now that you're done testing on the local frontend There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To be honest, the link before was just a dummy link, and since I added the default dummy link to the MerchFactory, I think it is no longer necessary to have it here. Do you think it is better to declare it explicitly instead? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As long as there's no issues, I think it's fine to have it in the MerchFactory since it's a generic property of all merch item photos. If we do this though, maybe we should consider abstracting away any other common properties for seed data that we create. not high priority but something to keep in mind |
||
uploadedPhoto: 'https://www.fakepicture.com/', | ||
position: 1, | ||
}); | ||
const MERCH_ITEM_1_PHOTO_2 = MerchFactory.fakePhoto({ | ||
|
@@ -542,7 +541,6 @@ async function seed(): Promise<void> { | |
]; | ||
const MERCH_ITEM_2_PHOTO_0 = MerchFactory.fakePhoto({ | ||
merchItem: MERCH_ITEM_2, | ||
uploadedPhoto: 'https://www.fakepicture.com/', | ||
position: 0, | ||
}); | ||
const MERCH_ITEM_2_PHOTO_1 = MerchFactory.fakePhoto({ | ||
|
@@ -591,7 +589,6 @@ async function seed(): Promise<void> { | |
}); | ||
const MERCH_ITEM_3_PHOTO_1 = MerchFactory.fakePhoto({ | ||
merchItem: MERCH_ITEM_3, | ||
uploadedPhoto: 'https://www.fakepicture.com/', | ||
position: 1, | ||
}); | ||
const MERCH_ITEM_3_PHOTO_2 = MerchFactory.fakePhoto({ | ||
|
@@ -601,12 +598,10 @@ async function seed(): Promise<void> { | |
}); | ||
const MERCH_ITEM_3_PHOTO_3 = MerchFactory.fakePhoto({ | ||
merchItem: MERCH_ITEM_3, | ||
uploadedPhoto: 'https://www.fakepicture.com/', | ||
position: 3, | ||
}); | ||
const MERCH_ITEM_3_PHOTO_4 = MerchFactory.fakePhoto({ | ||
merchItem: MERCH_ITEM_3, | ||
uploadedPhoto: 'https://www.fakepicture.com/', | ||
position: 4, | ||
}); | ||
MERCH_ITEM_3.merchPhotos = [ | ||
|
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.
are we consistent with declaring numbers like this at the top of the file or do we generally do this in the Config? small nit either way but for the sake of consistency