[Interactive Graph] Update the builder with all currently migrated graph types

[nishasy]

Summary:

I updated the builder utility with all currently migrated graph types. This
meant adding linear, linear system, ray, quadratic, and sinusoid.

I also added the ability to give them all starting coords. This is necessary
to prove that the starting coords can be set at all.

Now that it's clear they can be set, we can move onto adding the ability
to edit these coordinates in the editor UI in the next task.

NOTE: The task also includes start coords for the Points graph type, but
that doesn't seem to have the mafs flag on in storybook yet, so I didn't
include that here.

Issue: https://khanacademy.atlassian.net/browse/LEMS-2051

Test plan:

Storybook

• segment
• multiple segments
• linear
• linear system
• ray
• circle
• quadratic
• sinusoid

Storybook previews showing custom start coords

segment	segments	linear
linear system	ray	circle
quadratic	sinusoid

[github-actions]

Size Change: -833 B (-0.1%)

Total Size: 845 kB

Filename	Size	Change
packages/perseus/dist/es/index.js	407 kB	-833 B (-0.2%)

ℹ️ View Unchanged

Filename	Size
packages/kas/dist/es/index.js	38.2 kB
packages/kmath/dist/es/index.js	4.26 kB
packages/math-input/dist/es/index.js	80.1 kB
packages/math-input/dist/es/strings.js	1.73 kB
packages/perseus-core/dist/es/index.js	906 B
packages/perseus-editor/dist/es/index.js	272 kB
packages/perseus-error/dist/es/index.js	866 B
packages/perseus-linter/dist/es/index.js	21.8 kB
packages/perseus/dist/es/strings.js	3.21 kB
packages/pure-markdown/dist/es/index.js	3.67 kB
packages/simple-markdown/dist/es/index.js	12.4 kB

_{compressed-size-action}

[khan-actions-bot]

Gerald

Required Reviewers

• @Khan/perseus for changes to .changeset/short-badgers-wonder.md, packages/perseus-editor/src/__stories__/editor-page.stories.tsx, packages/perseus/src/widgets/__stories__/interactive-graph-regression.stories.tsx, packages/perseus/src/widgets/__testdata__/interactive-graph.testdata.ts, packages/perseus/src/widgets/interactive-graphs/interactive-graph-question-builder.test.ts, packages/perseus/src/widgets/interactive-graphs/interactive-graph-question-builder.ts

---

Don't want to be involved in this pull request? Comment #removeme and we won't notify you of further changes.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.92%. Comparing base (8cbfeba) to head (4389efc).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1373      +/-   ##
==========================================
+ Coverage   69.68%   70.92%   +1.24%     
==========================================
  Files         492      495       +3     
  Lines      103871   103927      +56     
  Branches     7505    10556    +3051     
==========================================
+ Hits        72382    73710    +1328     
+ Misses      31310    30217    -1093     
+ Partials      179        0     -179     

Files	Coverage Δ
...widgets/__testdata__/interactive-graph.testdata.ts	100.00% <100.00%> (ø)
...ctive-graphs/interactive-graph-question-builder.ts	100.00% <100.00%> (ø)

... and 147 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8cbfeba...4389efc. Read the comment docs.

[benchristel]

Looks great, thank you! My one question is whether we want to let callers of the builder pass both startCoords and numSegments to the segment graph. In the common case, the information in numSegments is redundant and could be derived from startCoords. I could maybe see an argument that we'd want to let numSegments be different from startCoords in order to test what happens when the data is inconsistent. That's such an edge case, though, that I don't think it's worth complicating the builder for the sake of the O(1) tests we might write that take advantage of it.

I'll leave the decision up to you, though.

[nishasy]

@benchristel I think it's still nice to have numSegments because it's accurate to the experience when coords isn't used. It would be nice to use the builder to create the segment graph with the default coords for a number of segments rather than having to find out and type all the coords out.

[github-actions]

npm Snapshot: Published

Good news!! We've packaged up the latest commit from this PR (4389efc) and published it to npm. You
can install it using the tag PR1373.

Example:

yarn add @khanacademy/perseus@PR1373

If you are working in Khan Academy's webapp, you can run:

./dev/tools/bump_perseus_version.sh -t PR1373

[benchristel]

It would be nice to use the builder to create the segment graph with the default coords for a number of segments rather than having to find out and type all the coords out.

I agree. I guess the way I'd prefer to accomplish that is by having a separate method to set non-default coords, so you could do either:

const question = interactiveGraphBuilder()
  .withNumSegments(3)
  .build();

or

const question = interactiveGraphBuilder()
  .withSegments([
    // ...
  ])
  .build();