Alter tests - needs mock data to be faster

If you really prefer to avoid stubs, it's probably best to close the PR without merging. It may be worth a short comment in issue #567 so other people know.

Bump actions/checkout from 3.4.0 to 3.5.0 (#64)

Bumps actions/checkout from 3.4.0 to 3.5.0.

• Release notes
• Changelog
• Commits

updated-dependencies:

• dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps actions/checkout from 3.4.0 to 3.5.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Maybe we could compromise by keeping stubs for early exercises where students may be really new to the language: documents-lasagna, annalyns-infiltration, tech-palace, and removing them for more advanced exercises (either blank or with comments). In most cases, instructions.md gives the format of each function, and runtests.jl will always show it.

I'd be fine with that though it still makes learning through spaced repetition harder as you want to repeat things very frequently early on. documented-lasagna is an edge case that should have the examplar solution of lasagna as stub anyway, regardless of its position in the track.

Fix JS tests, add test data for editor request options

It's not just we don't need negative values, but in this case it should not.

Your track, your choice.

Maybe we could compromise by keeping stubs for early exercises where students may be really new to the language: documents-lasagna, annalyns-infiltration, tech-palace, and removing them for more advanced exercises (either blank or with comments). In most cases, instructions.md gives the format of each function, and runtests.jl will always show it.

It's not just we don't need negative values, but in this case it should not.

I agree that stubs are unnecessary but harmless. They are also Exercism policy for concept exercises, so we're kind of stuck with them.

Empty stubs satisfy the requirement that they must be present and serve the purpose for making it clear where the student needs to add code. The other statements in the spec leave room for interpretation and imho empty stubs are in line with the spec. Clearly we shouldn't provide stubs for ifs either, even if the exercise doesn't introduce them.

I think the principle of minimum surprise can be useful in teaching new content.

Spaced repetition is one of the most effective learning methods and while the function syntax is fairly trivial, you're still taking away learning opportunities from students by removing the need to practice what has been introduced before (when to use what syntax? Should a function use a keyword arg or be two definitions? etc).

I stand by that these stubs make the exercise worse and take away learning opportunities from the student. If the spec is bad in that regard, we should ignore it (even if I think empty stubs are in line with it). It's not like leaving them empty will break the site.

Build(deps): bump actions/checkout from 3.4.0 to 3.5.0 (#85)

Bumps actions/checkout from 3.4.0 to 3.5.0.

• Release notes
• Changelog
• Commits

updated-dependencies:

• dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps actions/checkout from 3.4.0 to 3.5.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

docs(nudge.tsx): fix typo in prompt (#3603)

https://github.com/exercism/exercism/issues/6673

Merge branch 'main' into add-real-time-feedback-modal

Handle celebratory

I agree that stubs are unnecessary but harmless. They are also Exercism policy for concept exercises, so we're kind of stuck with them.

The different ways to define functions were covered in lasagna, which students had to complete before unlocking any of these exercises. Several other language tracks (including those highlighted in Functional February) have equivalent long/short forms, and there is an informal convention to stub the long form and let students shorten it if appropriate. I think the principle of minimum surprise can be useful in teaching new content.

The exception is when function syntax is the point of the exercise. This was the case with lasagna, and will be true again when we reach multiple-dispatch. On that point, I have some doubts about stubbing the two loot methods in annalyns-infiltration2, but that exercise still has multiple issues to deal with and is well down the concept exercise flowchart, so we can maybe save the argument for another day.

Bumps @types/node from 18.15.7 to 18.15.10.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

:arrow_up: Bump phpstan/phpstan from 1.10.7 to 1.10.8

Bumps phpstan/phpstan from 1.10.7 to 1.10.8.

• Release notes
• Changelog
• Commits

updated-dependencies:

• dependency-name: phpstan/phpstan dependency-type: direct:development update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] support@github.com

Bumps phpstan/phpstan from 1.10.7 to 1.10.8.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Fix typo in Nudge

Refactor

This is the PR in response to this topic in the forum. The Javascript version has many more flaws, which I'll correct after this PR is merged.