Add /uploadActivities

[JosephVolosin]

This PR adds the route /uploadActivities which allows uploading of a set of activities to a plan. The activities are expected in the plan JSON format.

See UI pull-request: NASA-AMMOS/plandev-ui#1843

[JosephVolosin]

Linter seems to be upset with how createdTags is being used:

Error: src/packages/plan/plan.ts(253,17): error TS6133: 'createdTags' is declared but its value is never read.
Error: src/packages/plan/plan.ts(396,13): error TS6133: 'createdTags' is declared but its value is never read.

Any ideas? I assume its cause its set in the try but only used in the catch

[duranb]

Linter seems to be upset with how createdTags is being used:

Error: src/packages/plan/plan.ts(253,17): error TS6133: 'createdTags' is declared but its value is never read.
Error: src/packages/plan/plan.ts(396,13): error TS6133: 'createdTags' is declared but its value is never read.

Any ideas? I assume its cause its set in the try but only used in the catch

For the first error, it doesn't look like you're using the createdTags array anywhere within the importPlan function. I believe it's because it now exists and is used within the createTags function you just created.

The second error looks like it's a scope issue. On line 391, you're declaring a const called createdTags, but on line 396, you're declaring another one within the try scope. The catch block doesn't have access to the last one created, just the one created on line 391. Effectively, the catch will never see a populated createdTags array.

[JosephVolosin]

Linter seems to be upset with how createdTags is being used:

Error: src/packages/plan/plan.ts(253,17): error TS6133: 'createdTags' is declared but its value is never read.
Error: src/packages/plan/plan.ts(396,13): error TS6133: 'createdTags' is declared but its value is never read.

Any ideas? I assume its cause its set in the try but only used in the catch

For the first error, it doesn't look like you're using the createdTags array anywhere within the importPlan function. I believe it's because it now exists and is used within the createTags function you just created.

The second error looks like it's a scope issue. On line 391, you're declaring a const called createdTags, but on line 396, you're declaring another one within the try scope. The catch block doesn't have access to the last one created, just the one created on line 391. Effectively, the catch will never see a populated createdTags array.

I think it should be good now - I had to create both createdTags and tagMap prior to the try/catch and then set it from the result, seems like the linter is happy and createdTags should be full when referenced

[duranb]

I think this is pretty much good to go! Just one small rename request. Thanks!

[duranb]

Thank you!