78 - Create the boilerplate of the dataset page #96

MellyGray · 2023-05-12T07:25:24Z

What this PR does / why we need it:

This PR is the spike issue for the frontend work for this feature

Create the boilerplate of the Dataset section with Dataset title #58

Here we add the Dataset page.

Features:

Dataset Title
Dataset Labels
Basic Layout to include the rest of the components as we develop them

Route:

datasets/{id}.

States:

Loading
Show the Dataset Information
Page Not Found

Which issue(s) this PR closes:

Closes [Spike - Frontend] Create the boilerplate of the Dataset section with Dataset title #78

Special notes for your reviewer:

I had to add some text for the blocks that do no exist yet such as the CitationBlock because I cannot create a Col/Row without nothing inside.
The e2e has been mocked, so if you go in the browser to /datasets/12345 you will see a Dataset with mocked values. This will be replaced in the future by the real call to js-dataverse. Or if we do not want this mock I can remove it.
I had to remove CSS cascade layers from de dataverse-design-system because Vite does not support injecting styles in Lib Mode, check this issue . Since Vite does not support this I had to use a plugin vite-plugin-libcss which does not support cascade layers. We can still use cascade layers in the main app.
The version label is in a lighter sade of grey than the one in the mock because it's the secondary color applied by bootstrap to all the elements of the design system
I had to remove the proxy configuration in the vite.config.ts to be able to run the npm start command. So we'll need to open a new issue to restore the proxy without breaking the command.

Suggestions on how to test this:

Application

npm install

cd packages/design-system && npm run build

cd back to the root.

Check that you have a .env file such as the .env.example, with the VITE_DATAVERSE_BACKEND_URL variable pointing to you local dataverse installation or if you don't have Dataverse running locally, you can point to https://demo.dataverse.org although some functionalities may not work

npm start

Go to http://localhost:5173/spa/datasets/12345

You will see the Datasets page with a mocked api call

Storybook

To see all the different states:

npm run storybook

Go to the Dataset section to see the different states of the page

Tests

npm run test:unit

or

npm run start

npm run test:e2e

Just remember that the e2e tests are not finished because the js-dataverse module is not ready

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Dataset Page added to the application.

Additional documentation:

…into feature/78-create-the-boilerplate-of-the-dataset-page

pdurbin

@MellyGray I made an initial pass of changed files. It feels like we're losing some things such as layers and the recent addition of the containerized dev environment. Can you please take a look? Thanks.

pdurbin · 2023-05-15T13:36:12Z

.env

@@ -1 +1 @@
-VITE_DATAVERSE_BACKEND_URL=http://localhost:8080
+VITE_DATAVERSE_BACKEND_URL=http://http://localhost:8000


Is this right? Double http?

You're right, that's wrong. I was also thinking, should we add the .env to the .gitignore?

pdurbin · 2023-05-15T13:37:24Z

dev-env/docker-compose-dev.yml

It doesn't seem right to delete this docker compose file. It was just added by @GPortas in in this PR:

65 - Containerized development environment #87

Wow, my bad, restored!

pdurbin · 2023-05-15T13:38:24Z

packages/design-system/.nyc_output/out.json

What is the purpose of this file?

Should we git rm it?

And then add it to .gitignore?

I'm asking because I see similar entries there:

$ ack .nyc_output .gitignore 15:/.nyc_output 19:.nyc_output

Yes, I added packages/design-system/.nyc_output to the gitignore, thanks!

pdurbin · 2023-05-15T13:40:47Z

packages/design-system/src/lib/components/badge/Badge.module.scss

-    .primary {
-        color: color-contrast($dv-primary-color);
-    }
+.primary:not(#\#) {


No more layers? Are we removing layers?

I tried to explain it in the PR description

I had to remove CSS cascade layers from de dataverse-design-system because Vite does not support injecting styles in Lib Mode, vitejs/vite#1579 . Since Vite does not support this I had to use a plugin vite-plugin-libcss which does not support cascade layers. We can still use cascade layers in the main app.

Cascade layers are not supported by the preprocessor for the Lib Mode of the design system

But we can still use cascade layers in the main application

We can create an issue to try to do some workaround for this

pdurbin · 2023-05-15T13:41:45Z

public/locales/en/pageNotFound.json

@@ -0,0 +1,4 @@
+{
+  "heading": "Page Not Found",
+  "message": "The page you are looking for was not found. If you believe this is an error, please contact Demo Dataverse Support for assistance."


This is fine for now, I suppose, but in the future, instead of "Demo Dataverse Support" as a hard-coded string, we'll want to pull this from the backend.

Yes, I saw there is a Modal to contact Dataverse Support, we can create a new issue to add this feature

pdurbin · 2023-05-15T13:43:13Z

vite.config.ts

-    host: true,
-    port: 5173,
-    hmr: {
-      clientPort: 8000 // nginx reverse proxy port


I'm pretty sure this nginx stuff is also something that was added in the recently "dev env" PR.

Yes, this code was added for the dev-env to work, but it's breaking the npm start command. You can test it in the develop branch if you run npm start and you go to the browser

So I asked Guillermo about this and he said he'll work on fixing it, but for the moment this was a workaround to be able to use npm start

Should I comment the code instead of removing it?

If we are basically reverting this PR about adding a docker compose dev environment...

65 - Containerized development environment #87

... @MellyGray can you please add this under "Special notes for your reviewer"?

@GPortas should we re-open the following issue?

Setup local development environment for Dataverse backend #65

Or perhaps create a new issue and put it on the schedule?

I just asked about this during a frontend meeting and new commits have been added to bring back the docker compose file. I'll take a look!

The docker-compose is back, but the nginx reverse proxy port I had to remove it to fix the npm start . So we still need to manage that with a new issue

@GPortas can you please create an issue for nginx? ^^

pdurbin · 2023-05-15T16:42:33Z

Currently, the README says Storybook is on port 6006...

$ grep 6006 README.md
Open [http://localhost:6006](http://localhost:6006) to view it in your browser.

... but these days it seems like Storybook is on both 6006 and 6007.

I was confused because I didn't realize at first that two browser are being opened. I only saw 6007 (which opened second, at least on my machine) and was wondering where the pages and layouts are. 🤔

Here the are! On the other port. Can we please update the README about this? I can only assume this is all by design. (I'm not sure if this behavior is new as of this PR or not.)

MellyGray · 2023-05-16T08:09:22Z

Currently, the README says Storybook is on port 6006...

Thanks! I updated the README. We have two instances of Storybook one for the Design System and one for the application.

I'm still trying to figure out the development workflow so for the moment I think two instances are helpful, but we'll see. We could be moving everything to 1 Storybook in the future if this configuration doesn't help the development workflow

MellyGray · 2023-05-16T08:10:22Z

I added a change in the Style Guide to the README

pdurbin

I'm having trouble running npm run test:e2e.

pdurbin · 2023-05-16T13:50:34Z

tests/e2e/sections/dataset/Dataset.spec.tsx

@@ -0,0 +1,17 @@
+describe('Dataset', () => {
+  it('successfully loads a dataset when passing the id', () => {
+    cy.visit('/dataset/12345')


I'm getting a failure when trying to reach this URL. Should it have /spa in it?

Running: sections/dataset/Dataset.spec.tsx (2 of 4) Dataset 1) successfully loads a dataset when passing the id 2) renders Hello Dataverse when no id is provided 0 passing (190ms) 2 failing 1) Dataset successfully loads a dataset when passing the id: CypressError: `cy.visit()` failed trying to load: http://localhost:5173/dataset/12345 The response we received from your web server was: > 404: Not Found This was considered a failure because the status code was not `2xx`. If you do not want status codes to cause failures pass the option: `failOnStatusCode: false` at <unknown> (http://localhost:5173/__cypress/runner/cypress_runner.js:147661:84) at visitFailedByErr (http://localhost:5173/__cypress/runner/cypress_runner.js:147069:12) at <unknown> (http://localhost:5173/__cypress/runner/cypress_runner.js:147644:13) at tryCatcher (http://localhost:5173/__cypress/runner/cypress_runner.js:18744:23) at Promise._settlePromiseFromHandler (http://localhost:5173/__cypress/runner/cypress_runner.js:16679:31) at Promise._settlePromise (http://localhost:5173/__cypress/runner/cypress_runner.js:16736:18) at Promise._settlePromise0 (http://localhost:5173/__cypress/runner/cypress_runner.js:16781:10) at Promise._settlePromises (http://localhost:5173/__cypress/runner/cypress_runner.js:16857:18) at _drainQueueStep (http://localhost:5173/__cypress/runner/cypress_runner.js:13451:12) at _drainQueue (http://localhost:5173/__cypress/runner/cypress_runner.js:13444:9) at ../../node_modules/bluebird/js/release/async.js.Async._drainQueues (http://localhost:5173/__cypress/runner/cypress_runner.js:13460:5) at Async.drainQueues (http://localhost:5173/__cypress/runner/cypress_runner.js:13330:14) From Your Spec Code: at Context.eval (http://localhost:5173/__cypress/tests?p=tests/e2e/sections/dataset/Dataset.spec.tsx:7:10) 2) Dataset renders Hello Dataverse when no id is provided: CypressError: `cy.visit()` failed trying to load: http://localhost:5173/dataset The response we received from your web server was: > 404: Not Found This was considered a failure because the status code was not `2xx`. If you do not want status codes to cause failures pass the option: `failOnStatusCode: false` at <unknown> (http://localhost:5173/__cypress/runner/cypress_runner.js:147661:84) at visitFailedByErr (http://localhost:5173/__cypress/runner/cypress_runner.js:147069:12) at <unknown> (http://localhost:5173/__cypress/runner/cypress_runner.js:147644:13) at tryCatcher (http://localhost:5173/__cypress/runner/cypress_runner.js:18744:23) at Promise._settlePromiseFromHandler (http://localhost:5173/__cypress/runner/cypress_runner.js:16679:31) at Promise._settlePromise (http://localhost:5173/__cypress/runner/cypress_runner.js:16736:18) at Promise._settlePromise0 (http://localhost:5173/__cypress/runner/cypress_runner.js:16781:10) at Promise._settlePromises (http://localhost:5173/__cypress/runner/cypress_runner.js:16857:18) at _drainQueueStep (http://localhost:5173/__cypress/runner/cypress_runner.js:13451:12) at _drainQueue (http://localhost:5173/__cypress/runner/cypress_runner.js:13444:9) at ../../node_modules/bluebird/js/release/async.js.Async._drainQueues (http://localhost:5173/__cypress/runner/cypress_runner.js:13460:5) at Async.drainQueues (http://localhost:5173/__cypress/runner/cypress_runner.js:13330:14) From Your Spec Code: at Context.eval (http://localhost:5173/__cypress/tests?p=tests/e2e/sections/dataset/Dataset.spec.tsx:13:10)

Yes, I updated the Cypress configuration to run on /spa. Thanks!

pdurbin · 2023-05-16T13:53:31Z

tests/e2e/sections/dataset/Dataset.spec.tsx

I'm not sure where to report this but I'm having trouble running the e2e tests. It's complaining that I'm missing the chai dependency:

Running: info/infrastructure/repositories/DataverseInfoJSDataverseRepository. (3 of 4) spec.ts [vite]: Rollup failed to resolve import "chai" from "/Users/pdurbin/github/iqss/dataverse-frontend/tests/e2e/info/infrastructure/repositories/DataverseInfoJSDataverseRepository.spec.ts". This is most likely unintended because it can break your application at runtime. If you do want to externalize this module explicitly add it to `build.rollupOptions.external` Oops...we found an error preparing this test file: > tests/e2e/info/infrastructure/repositories/DataverseInfoJSDataverseRepository.spec.ts The error was: Error: [vite]: Rollup failed to resolve import "chai" from "/Users/pdurbin/github/iqss/dataverse-frontend/tests/e2e/info/infrastructure/repositories/DataverseInfoJSDataverseRepository.spec.ts". This is most likely unintended because it can break your application at runtime. If you do want to externalize this module explicitly add it to `build.rollupOptions.external` at onRollupWarning (file:///Users/pdurbin/github/iqss/dataverse-frontend/node_modules/vite/dist/node/chunks/dep-b6b8dfbf.js:44766:19) at onwarn (file:///Users/pdurbin/github/iqss/dataverse-frontend/node_modules/vite/dist/node/chunks/dep-b6b8dfbf.js:44536:13) at Object.onwarn (file:///Users/pdurbin/github/iqss/dataverse-frontend/node_modules/rollup/dist/es/shared/node-entry.js:25305:13) at ModuleLoader.handleInvalidResolvedId (file:///Users/pdurbin/github/iqss/dataverse-frontend/node_modules/rollup/dist/es/shared/node-entry.js:23940:26) at file:///Users/pdurbin/github/iqss/dataverse-frontend/node_modules/rollup/dist/es/shared/node-entry.js:23900:26 at processTicksAndRejections (node:internal/process/task_queues:95:5) This occurred while Cypress was compiling and bundling your test code. This is usually caused by: - A missing file or dependency - A syntax error in the file or one of its dependencies Fix the error in your code and re-run your tests. (Results) ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Tests: 0 │ │ Passing: 0 │ │ Failing: 1 │ │ Pending: 0 │ │ Skipped: 0 │ │ Screenshots: 0 │ │ Video: false │ │ Duration: 0 seconds │ │ Spec Ran: info/infrastructure/repositories/DataverseInfoJSDataverseRepository.spec.ts │ └────────────────────────────────────────────────────────────────────────────────────────────────┘ ──────────────────────────────────────────────────────────────────────────────────────────────────── Running: users/infrastructure/repositories/UserJSDataverseRepository.spec.ts (4 of 4) [vite]: Rollup failed to resolve import "chai" from "/Users/pdurbin/github/iqss/dataverse-frontend/tests/e2e/users/infrastructure/repositories/UserJSDataverseRepository.spec.ts". This is most likely unintended because it can break your application at runtime. If you do want to externalize this module explicitly add it to `build.rollupOptions.external` Oops...we found an error preparing this test file: > tests/e2e/users/infrastructure/repositories/UserJSDataverseRepository.spec.ts The error was: Error: [vite]: Rollup failed to resolve import "chai" from "/Users/pdurbin/github/iqss/dataverse-frontend/tests/e2e/users/infrastructure/repositories/UserJSDataverseRepository.spec.ts". This is most likely unintended because it can break your application at runtime. If you do want to externalize this module explicitly add it to `build.rollupOptions.external` at onRollupWarning (file:///Users/pdurbin/github/iqss/dataverse-frontend/node_modules/vite/dist/node/chunks/dep-b6b8dfbf.js:44766:19) at onwarn (file:///Users/pdurbin/github/iqss/dataverse-frontend/node_modules/vite/dist/node/chunks/dep-b6b8dfbf.js:44536:13) at Object.onwarn (file:///Users/pdurbin/github/iqss/dataverse-frontend/node_modules/rollup/dist/es/shared/node-entry.js:25305:13) at ModuleLoader.handleInvalidResolvedId (file:///Users/pdurbin/github/iqss/dataverse-frontend/node_modules/rollup/dist/es/shared/node-entry.js:23940:26) at file:///Users/pdurbin/github/iqss/dataverse-frontend/node_modules/rollup/dist/es/shared/node-entry.js:23900:26 at processTicksAndRejections (node:internal/process/task_queues:95:5) This occurred while Cypress was compiling and bundling your test code. This is usually caused by: - A missing file or dependency - A syntax error in the file or one of its dependencies Fix the error in your code and re-run your tests. (Results) ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Tests: 0 │ │ Passing: 0 │ │ Failing: 1 │ │ Pending: 0 │ │ Skipped: 0 │ │ Screenshots: 0 │ │ Video: false │ │ Duration: 0 seconds │ │ Spec Ran: users/infrastructure/repositories/UserJSDataverseRepository.spec.ts │ └────────────────────────────────────────────────────────────────────────────────────────────────┘

The chai module was missing in the package.json, maybe because of some merge conflict. Thanks! You'll need to run npm install again to install the chai module

pdurbin · 2023-05-16T14:05:45Z

I made a few tweaks to the code:

35d7177 fix test:unit command
da8ed00 change to Dataverse Title to be more realistic #78
1d5bb86 clean up Changes from the Style Guide #78

http://localhost:5173/spa/datasets/12345 looks fine. Here's how it looks for me (I made it "Dataset Title" to be a bit more realistic):

I'm basically ready to approve this accept that I can't get the e2e tests running. Please see #96 (review)

MellyGray · 2023-05-16T14:35:35Z

I made a few tweaks to the code:

Thanks! I fixed the e2e tests for the Dataset page, although we don't have much to test since the js-dataverse module hasn't implemented the dataset endpoint yet

pdurbin

Overall, this looks fine to me so I'm moving it to QA.

However, please note that e2e tests are known to be failing:

"Yes, the UserJSDataverseRepository e2e tests are not working yet, but this comes from the login logout branch, is not because of the Dataset changes.

Since we need to log in in JSF and use that cookie in the SPA, we still do not have those tests working"

-- @MellyGray at https://iqss.slack.com/archives/C04MJ76A34Z/p1684252920863049?thread_ts=1684246047.311379&cid=C04MJ76A34Z

I assume we'll fix these in a future PR.

pdurbin · 2023-05-16T16:22:55Z

@kcondon please note that this PR should be merged before #91 (which doesn't yet target develop).

kcondon · 2023-05-16T20:42:47Z

I might need some help setting this up (Check that you have .env with a backend url). For QA, would this be using the deploy to payara action, making sure I have develop Dataverse already deployed to the same box?

I'm getting errors on npm start
([ERROR] [plugin vite:dep-scan] Failed to resolve entry for package "dataverse-design-system". The package may have incorrect main/module/exports specified in its package.json.)
Errors using Dataset component in storybook: importing a module script failed
Unit tests failed also: [vite] Internal server error: Failed to resolve entry for package "dataverse-design-system". The package may have incorrect main/module/exports specified in its package.json.

MellyGray · 2023-05-17T08:18:36Z

I might need some help setting this up (Check that you have .env with a backend url). For QA, would this be using the deploy to payara action, making sure I have develop Dataverse already deployed to the same box?

The .env with a backend url means that you need to create a .env such as the .env.example with the VITE_DATAVERSE_BACKEND_URL pointing to your local dataverse installation.

If you use the payara deployment then you don't need to set the .env, the .env is just for running the application locally using npm start command.

Try cd packages/design-system && npm run build then try again npm start. Sorry, I forgot that you need to build the "dataverse-design-system"
This one may be because of 1, but let me know if that didn't fixed it
Same with this one, try 1 and check if you can run the tests

Sorry! I forgot that step

kcondon · 2023-05-17T09:02:25Z

@MellyGray Thanks, that works now. I am seeing two e2e tests failing. Is this expected at this time?
User JSDataverse Repository
1) gets the authenticated user
2) removes the authenticated user

0 passing (309ms)
2 failing

User JSDataverse Repository
gets the authenticated user:
Error: Cannot read properties of undefined (reading 'status')

Otherwise, this looks good and I can merge it.

OK, I see from Phil's comment about and link to Slack conversation it is expected. So, merging!
Melina Hernández
17 hours ago
Yes, the UserJSDataverseRepository e2e tests are not working yet, but this comes from the login logout branch, is not because of the Dataset changes.

…e-of-the-dataset-page 78 - Create the boilerplate of the dataset page

MellyGray added 9 commits May 4, 2023 12:14

feat(Dataset): add new page

0cfc139

feat(DatasetBoilerplate): show Dataset title in the Dataset page

f8f0af3

feat(DatasetBoilerplate): add data version number

60ba868

feat(Dataset Boilerplate): add DatasetLabels component

4a82000

feat(Dataset Boilerplate): add LoadingProvider

a0c2b83

feat(Dataset Boilerplate): handle isLoading and no dataset found states

da3a714

feat(Dataset Boilerplate): add tests for Dataset page states

1f5e840

feat(Dataset Boilerplate): get dataset id from route parameters

3155cb4

fix(Github Action): modify test to run on github actions

06641d4

MellyGray linked an issue May 12, 2023 that may be closed by this pull request

[Spike - Frontend] Create the boilerplate of the Dataset section with Dataset title #78

Closed

MellyGray added 7 commits May 12, 2023 11:58

Merge branch 'develop' of https://github.com/IQSS/dataverse-frontend …

b10394e

…into feature/78-create-the-boilerplate-of-the-dataset-page

fix(Design System): remove cascade layers

29a611d

fix(npm start): remove server

3574cda

fix(coverage): add tests

04aeac4

feat(PageNotFound): use the Alert component

e01b97e

feat(Dataset Boilerplate): add translations

f50dbf7

fix(Route): datasets route in plural

596a0aa

MellyGray marked this pull request as ready for review May 12, 2023 12:13

MellyGray added the Size: 10 A percentage of a sprint. 7 hours. label May 12, 2023

pdurbin self-assigned this May 12, 2023

pdurbin reviewed May 15, 2023

View reviewed changes

pdurbin assigned MellyGray May 15, 2023

MellyGray added 3 commits May 15, 2023 16:08

fix(dev-env):restore dev-env files

d245c4a

fix: add packages/design-system/.nyc_output to .gitignore

10b0bcf

fix(.env): typo in backend_url

3d7e8e8

MellyGray added 2 commits May 16, 2023 09:52

fix(README): update Storybook ports

5659f05

feat(README): add change in the style guide

bd45ca2

MellyGray removed their assignment May 16, 2023

pdurbin added 3 commits May 16, 2023 09:14

clean up Changes from the Style Guide #78

1d5bb86

change to Dataverse Title to be more realistic #78

da8ed00

fix test:unit command

35d7177

pdurbin reviewed May 16, 2023

View reviewed changes

pdurbin assigned MellyGray May 16, 2023

fix(e2e): missing configuration details

5291c38

MellyGray removed their assignment May 16, 2023

pdurbin approved these changes May 16, 2023

View reviewed changes

pdurbin removed their assignment May 16, 2023

kcondon self-assigned this May 16, 2023

kcondon merged commit e006d89 into develop May 17, 2023

kcondon deleted the feature/78-create-the-boilerplate-of-the-dataset-page branch May 17, 2023 09:10

jayanthkomarraju pushed a commit to jayanthkomarraju/dataverse-frontend that referenced this pull request May 31, 2024

Merge pull request IQSS#96 from IQSS/feature/78-create-the-boilerplat…

7be5dd7

…e-of-the-dataset-page 78 - Create the boilerplate of the dataset page

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

78 - Create the boilerplate of the dataset page #96

78 - Create the boilerplate of the dataset page #96

MellyGray commented May 12, 2023 •

edited

Loading

pdurbin left a comment

pdurbin May 15, 2023

MellyGray May 15, 2023 •

edited

Loading

pdurbin May 15, 2023

MellyGray May 15, 2023

pdurbin May 15, 2023

MellyGray May 15, 2023

pdurbin May 15, 2023

MellyGray May 15, 2023

pdurbin May 15, 2023

MellyGray May 15, 2023

pdurbin May 15, 2023

MellyGray May 15, 2023

pdurbin May 15, 2023

pdurbin May 15, 2023

MellyGray May 15, 2023

pdurbin May 15, 2023

pdurbin commented May 15, 2023

MellyGray commented May 16, 2023

MellyGray commented May 16, 2023

pdurbin left a comment

pdurbin May 16, 2023

MellyGray May 16, 2023

pdurbin May 16, 2023

MellyGray May 16, 2023 •

edited

Loading

pdurbin commented May 16, 2023

MellyGray commented May 16, 2023

pdurbin left a comment

pdurbin commented May 16, 2023

kcondon commented May 16, 2023 •

edited

Loading

MellyGray commented May 17, 2023

kcondon commented May 17, 2023 •

edited

Loading

		@@ -1 +1 @@
		VITE_DATAVERSE_BACKEND_URL=http://localhost:8080
		VITE_DATAVERSE_BACKEND_URL=http://http://localhost:8000

78 - Create the boilerplate of the dataset page #96

78 - Create the boilerplate of the dataset page #96

Conversation

MellyGray commented May 12, 2023 • edited Loading

What this PR does / why we need it:

Which issue(s) this PR closes:

Special notes for your reviewer:

Suggestions on how to test this:

Application

Storybook

Tests

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Additional documentation:

pdurbin left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

MellyGray May 15, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pdurbin commented May 15, 2023

MellyGray commented May 16, 2023

MellyGray commented May 16, 2023

pdurbin left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

MellyGray May 16, 2023 • edited Loading

Choose a reason for hiding this comment

pdurbin commented May 16, 2023

MellyGray commented May 16, 2023

pdurbin left a comment

Choose a reason for hiding this comment

pdurbin commented May 16, 2023

kcondon commented May 16, 2023 • edited Loading

MellyGray commented May 17, 2023

kcondon commented May 17, 2023 • edited Loading

MellyGray commented May 12, 2023 •

edited

Loading

MellyGray May 15, 2023 •

edited

Loading

MellyGray May 16, 2023 •

edited

Loading

kcondon commented May 16, 2023 •

edited

Loading

kcondon commented May 17, 2023 •

edited

Loading