Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show students what packages are available in the test runner #1045

Open
petertseng opened this issue Feb 6, 2022 · 5 comments
Open

Show students what packages are available in the test runner #1045

petertseng opened this issue Feb 6, 2022 · 5 comments

Comments

@petertseng
Copy link
Member

The test runner only has a limited set of packages, since it is forbidden from having internet access. If a student submits a package.yaml with a package that is not in that set, there will be an error. To give students a better idea of what packages the test runner has, instead of forcing them to resort to trial and error, the track documentation shown to the students should allow them to discover this. Suggestion for how to do this:

Add an explanation to https://github.com/exercism/haskell/blob/main/docs/TESTS.md#using-packages, containing the following points (which you can paraphrase or refine as necessary):

@asarkar

This comment was marked as off-topic.

@asarkar

This comment was marked as off-topic.

@petertseng
Copy link
Member Author

Now that I have addressed the above by approving the above PR, we should remember to keep discussion on topic. This issue is about updating the instructions, and discussions in this issue should be focused on that (e.g. questions about how to word the instructions or where exactly they should go, etc.) Discussions about specific packages to be added should be discussed by opening a PR in the haskell-test-runner repo or by a separate issue in this repo.

@asarkar
Copy link

asarkar commented Jul 14, 2022

Discussions about specific packages to be added should be discussed by opening a PR in the haskell-test-runner repo

Sure, but if a PR sits unattended for a week, then the author has no choice but to try and raise maintainers, by commenting in a ticket where a recommendation has been explicitly made to open such PR. Such a comment can’t be penalized or written off as irrelevant.

@petertseng
Copy link
Member Author

Not to worry - no penalty has been applied that I am aware of, and if there is a penalty applied that I am not aware of, let this comment serve as my authorisation to rescind that penalty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants