quantified.uncertainty/squiggle
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

format

Browse Source
This commit is contained in:
Umur Ozkul 2022-08-23 09:38:12 +02:00
parent a394e93e06
commit b7ae9804a5
1 changed files with 6 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
packages/squiggle-lang/__tests__/ReducerProject/ReducerProject_tutorial_1_multisource_test.res
View File

@ -10,8 +10,7 @@ open Expect.Operators
describe("ReducerProject Tutorial", () => { describe("ReducerProject Tutorial", () => {
describe("Multi source", () => { describe("Multi source", () => {
/* /*
Case "Running multiple sources" Case "Running multiple sources" */
*/
test("Chaining", () => { test("Chaining", () => {
let project = Project.createProject() let project = Project.createProject()
/* This time let's add 3 sources and chain them together */ /* This time let's add 3 sources and chain them together */
@ -67,8 +66,7 @@ Case "Running multiple sources"
test("Intro to including", () => { test("Intro to including", () => {
/* Though it would not be practical for a storybook, /* Though it would not be practical for a storybook,
let's write the same project above with includes. let's write the same project above with includes.
You will see that parsing includes is setting the dependencies the same way as before. You will see that parsing includes is setting the dependencies the same way as before. */
*/
let project = Project.createProject() let project = Project.createProject()
/* This time source1 and source2 are not depending on anything */ /* This time source1 and source2 are not depending on anything */
@ -101,16 +99,14 @@ Case "Running multiple sources"
)->expect == ("Ok(())", "@{x: 1,y: 2,z: 3}") )->expect == ("Ok(())", "@{x: 1,y: 2,z: 3}")
/* /*
Doing it like this is too verbose for a storybook Doing it like this is too verbose for a storybook
But I hope you have seen the relation of setContinues and parseIncludes But I hope you have seen the relation of setContinues and parseIncludes */
*/
/* /*
Dealing with includes needs more. Dealing with includes needs more.
- There are parse errors - There are parse errors
- There are cyclic includes - There are cyclic includes
- And the depended source1 and source2 is not already there in the project - And the depended source1 and source2 is not already there in the project
- If you knew the includes before hand there would not be point of the include directive. - If you knew the includes before hand there would not be point of the include directive.
More on those on the next section. More on those on the next section. */
*/
}) })
}) })
}) })