Skip to content

Conversation

@atombear
Copy link

No description provided.

@MatthijsBlom
Copy link
Contributor

I suspect a patch to problem-specifications/zipper would be welcome as well.

@atombear
Copy link
Author

@MatthijsBlom sorry, what do you mean? is there anything else i should do for this pr? someone needs to kick the ci for me...

@petertseng
Copy link
Member

@MatthijsBlom
Copy link
Contributor

To elaborate: the tests are generated/derived from the problem specifications in the problem-specifications repo. This is done to make it easier to collectively maintain exercises among the many individual language tracks. I have repeatedly seen it suggested to send PR's to problem-specifications first/instead, hence my suggestion to approach them.

@atombear
Copy link
Author

@MatthijsBlom @petertseng how do i make the pr? ie, i can make a pr directly to that file, but it would seem at least that i need to supply a uuid? how do i derive that value?

@MatthijsBlom
Copy link
Contributor

I really don't know, but I'm sure the maintainers of the problem-specifications repo will tell you.

@petertseng
Copy link
Member

It is your choice how you generate the UUID, as long as it is a version 4 UUID.

@MatthijsBlom
Copy link
Contributor

Oh, silly me, of course it doesn't matter how it is generated: it is unique, after all!

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.

3 participants