Should the comments expand to the entire page rather than the length of the line it's associated with? Short bullet points now also get very narrow comment fields.

Also I'm not sure this meets the definition of done as laid out by #18. #18 mentions that "and include those comments in the badge / output", but I see no functionality for this.

Also I'm not sure this meets the definition of done as laid out by #18. #18 mentions that "and include those comments in the badge / output", but I see no functionality for this.

I wasn't able to make it to the meeting yesterday, so maybe it was decided then, but iirc we hadn't decided how we want the data to be formatted as output. (I see

Dorota will take our existing "schema" and turn it into a proper JSON schema.

in yesterday's meeting log).

This interactive subdirectory was built as a proof-of-concept prototype (hence the unaltered "Getting Started with Create React App" README) but seems to be becoming a working prototype. As it is, all the checks are stored in React state
, and I believe these comments are as well with this PR.

Of

1. Ability to add comments for each field
2. Ability to save a json/csv record of the completed form

― https://cmi-cnl.slack.com/archives/C05FXAZ316Z/p1694104612877259

(I'm not sure why we don't have an open issue for #​2), I think this PR resolves #​1 and including the comments in the badge/output is more of a requirement for the data display interface once #​2 is resolved.

Should the comments expand to the entire page rather than the length of the line it's associated with? Short bullet points now also get very narrow comment fields.

Makes sense to me. I doubt I'll prioritize this anytime soon though, if anyone else once to update the styling

@djarecka : I was talking to @shnizzedy and @nx10 about updating the web form, which would require this. @nx10 is willing to build out the schema, but just wanted to make sure he wasn't stepping on toes: that all-good from your side?

I haven't started working on this, so feel free to work on this! Thanks @nx10!

Superseded by #30