Feature/conversion title

[interim17]

Time estimate or Size

small
Will get review at UX office hours prior to merging, code ready for review.

Problem

Advances #396
Closes: #509

Solution

UI for input, and optional property on ConversionProcessingData for title.

Small tweaks to the naming of fileName and backendFileName for clarity in the file conversion logic.

Steps to Verify:

1. Send a Smoldyn file for conversion and provide a title, check that the title appears in the trajectory you receive back.
   (Tip: logging the data on line 271 in ViewerPanel.tsx in handleIncomingConvertedFile)

Screenshots (optional):

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	66.4% (-0.27% 🔻)	666/1003
🟡	Branches	65.31% (-0.9% 🔻)	96/147
🔴	Functions	35.41% (-0.42% 🔻)	91/257
🟡	Lines	64.7% (-0.21% 🔻)	592/915

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🔴	... / reducer.ts	20% (-1.43% 🔻)	100%	0%	20% (-1.43% 🔻)
🔴	... / actions.ts	51.28% (-0.07% 🔻)	100%	0%	51.28% (-0.07% 🔻)
🔴	... / logics.ts	15.35% (-0.14% 🔻)	0%	0%	15.77% (-0.07% 🔻)

Test suite run success

121 tests passing in 7 suites.

Report generated by 🧪jest coverage report action from 3fa65a0

[toloudis]

LGTM!

[tyler-foster]

LGTM.

Do we care about the overall test coverage going down? Should there be tests for e.g. the reducer.ts and logics.ts changes?

[interim17]

LGTM.

Do we care about the overall test coverage going down? Should there be tests for e.g. the reducer.ts and logics.ts changes?

Talked to Dan about this and at least for now he seems to feel comfortable with overall coverage dropping below the previous threshold.