Skip to content

Ozan's Playlist concept exercise#435

Merged
colinleach merged 4 commits intoexercism:mainfrom
colinleach:ozans-playlist
Feb 13, 2026
Merged

Ozan's Playlist concept exercise#435
colinleach merged 4 commits intoexercism:mainfrom
colinleach:ozans-playlist

Conversation

@colinleach
Copy link
Copy Markdown
Contributor

A simple one for set-operations. It's hard to avoid giving too much away in the hints, so I'm sort of tempted to cut it down to just the general advice.

Are the tests correctly numbered? I'm still a bit vague about what we agreed.

@colinleach colinleach requested a review from depial February 10, 2026 17:52
@colinleach
Copy link
Copy Markdown
Contributor Author

Delighted to see that CI passes, for the first time since the test runner update.

@depial
Copy link
Copy Markdown
Contributor

depial commented Feb 10, 2026

Are the tests correctly numbered?

Yep!

Delighted to see that CI passes, for the first time since the test runner update.

No R test runner updates yet (a couple for Julia's yesterday). I've made good headway with R's though and I'm trying to work out the details and corner cases. I've decided to try to write the test processing bit in R, so future maintainers can modify it without knowing Bash. This is proving troublesome though since there's no to_json function in Base R...

I'll try to get to reviewing here tonight, but I'm at about max levels of obsession with the test runner, so I can't make any promises.

@colinleach
Copy link
Copy Markdown
Contributor Author

there's no to_json function in Base R

If we need a small package like jsonlite or jsonify, it probably wouldn't be a problem to add that to the test runner. I'm sure anything like that would be tiny compared with ggplot2 (and a lot more useful, in context).

Copy link
Copy Markdown
Contributor

@depial depial left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one comment on the hints.md which highlights your point about being too specific. I think we're supposed to tend towards the more general, as you suggest, and here I think the exercise is so straightforward specificity is unnecessary anyways.

If you want to add something for Task 1 and Task 2 for completeness, maybe something like:

## 1. Remove duplicate tracks

- Remember that removing duplicates leaves you with the unique entries.

## 2. Check whether a track has already been added

- This is checking for inclusion, which we've already seen in previous concepts.

As long as that doesn't sound to patronizing... :D

Comment on lines +5 to +8
These are all short and simple tasks.
If you find yourself writing several lines of code in a function, please stop and read the introduction.

## 3. Add tracks
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if we need to have a complete list (from 1 to 5 here). I would venture a guess that it's not necessary, but that really is just a guess.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Point noted, but I'm curious to test whether hints need to be numbered consecutively from 1. Is it OK to merge this as-is and see how it looks?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May as well give it a look to see how the website reacts.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems absolutely fine. I think the Rails backend just looks for level-2 headers (starting with ## ).

@colinleach colinleach mentioned this pull request Feb 12, 2026
36 tasks
@colinleach colinleach merged commit 2977e83 into exercism:main Feb 13, 2026
3 checks passed
@depial
Copy link
Copy Markdown
Contributor

depial commented Feb 13, 2026

It looks like the hints button is still available and they pop up with just the name of the task. It might be better to add something...

image

@colinleach
Copy link
Copy Markdown
Contributor Author

OK, I didn't even know there was a hints button! I was looking under the Get Help tab, which is fine.

Looks like we'll be adding hints, though I'm more worried about Mixed Juices timing out.

@depial
Copy link
Copy Markdown
Contributor

depial commented Feb 13, 2026

I'm also getting a time out there...

@depial
Copy link
Copy Markdown
Contributor

depial commented Feb 13, 2026

I'm just about to push a PR with the print function for Task 3. Maybe that will sort something out?

@depial
Copy link
Copy Markdown
Contributor

depial commented Feb 13, 2026

OK, I didn't even know there was a hints button!

I think this came with v2 of the test runner :D

@colinleach colinleach deleted the ozans-playlist branch February 18, 2026 23:17
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

Successfully merging this pull request may close these issues.

2 participants