question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Problems with layout and tests for various Rosetta Code challenges

See original GitHub issue

This issue is just to track the changes we’re making to the layout of the descriptions and how the tests are rendered. Many of these are minor changes like moving the challenge instructions to the instructions section, or removing <p> tags and/or the space between the function name and the first parenthesis in the seed. I’ll submit a PR over the next few days.

More substantial changes are listed below:

  • 24 game: Fixed by @thecodingaviator in #35389
  • 9 billion names of God the integer: Removed the word “Task” and added <ul>
  • ABC Problem: Added <pre> section and <ul>. Reordered some text in the instructions section
  • Abundant, deficient and perfect number classifications: Added <pre> section, inline border style, and bolded some text
  • Accumulator factory: Bolded text, adjusted the description so it’s more like the one on Rosetta Code, and wrote new instructions
  • Ackermann function: Fixed MathJax function
  • Align columns: Added ordered list for rules
  • Amicable pairs: Bolded text, added <ol> for example section, removed the word “Task”, and removed the “Related Tasks” section
  • Averages/Pythagorean means: Added <ul> list and line breaks for math functions
  • Averages-Root mean square: Added italics and bolded some text
  • Babbage problem: Cleaned up block quote
  • Circles of given radius through two points: Added a couple of <ul>s and bolded some text
  • Closest-pair problem: Bolded text in the code samples, added a <ul> for the resources and further readings, and moved the resources list to the bottom of the description
  • Combinations: Bolded text
  • Comma quibbling: Added <ol> and <ul>
  • Compare a list of strings: Added <ul>
  • Convert seconds to compound duration: Added <ul>s and bolded text
  • Count occurrences of a substring: Added <ul>
  • Count the coins: Added <ul> sections and bolded text
  • Cramer’s rule: Cleaned up line breaks in description
  • Cut a rectangle: Fixed image
  • Date format: Added <ul> and bolded text
  • Date manipulation: Removed some line breaks
  • Day of the week: Removed the word “Task”
  • Deal cards for FreeCell: Added lists and bolded some text
  • Define a primitive data type: Added list, and removed unnecessary backslash escape characters and changed some single quotation marks to double quotation marks in the tests
  • Department Numbers: This challenge’s description and tests needs some work. Will submit a separate PR for this one.
  • Element-wise operations: Bolded text and added list
  • Emirp primes: Fixed spelling errors, made slight adjustments to description text, and added list
  • Equilibrium index: Added lists
  • Euler method: Added lists
  • Execute a Markov algorithm: Fixed <pre> sections in description and bolded text
  • Execute Brain****: Convert table to markdown table
  • Extensible prime generator: Add list
  • Factorial: Added list and bolded text
  • Factors of a Mersenne number: Added <pre>
  • Factors of an integer: Changed description from “Write a function that returns the factors of a positive integer” to “Write a function that returns the factors of a positive integer as an array”
  • Farey sequence: Added lists
  • Fibonacci n-step number sequences: Added lists and converted table to markdown table
  • Fibonacci word: Added <pre> and bolded text
  • Fractran: Added list and indented text
  • Gaussian elimination: Removed a period from the math function and added some line breaks
  • Generate lower case ASCII alphabet: Changed the example in the description to show that the function will be passed an array with two letters to represent the range, rather than two numbers
  • Gray code: Fixed code examples
  • Greatest subsequential sum: Adjusted spacing in some of the testString arrays so they’re consistent throughout
  • Hailstone sequence: Added lists
  • Happy numbers: Added link, bolded some text
  • Harshad or Niven series: Bolded text
  • Hash from two arrays: Added list
  • Hash join: Added lists, fixed <pre> section, and edited the instructions for clarity
  • Heronian triangles: Bolded text, fixed math functions and added a left margin to them
  • Hofstadter Figure-Figure sequences: Fixed math function and added a left margin to it, bolded text, added list
  • Hofstadter Q sequence: Fixed math function and added a left margin to it, and edited the instructions for clarity
  • I before E except after C: Fixed list and edited the instructions for clarity
  • Identity matrix: Fixed mathematical function and added list
  • Jaro distance: Bolded text, fixed list
  • S-Expressions: Fixed spacing, links, and <pre> section
  • Sailors, coconuts and a monkey problem: Fixed spacing, links, and bolded text
  • SEDOLs: Fixed spacing and made a edited the last sentence of the description slightly by removing the word “also” and adding “an”
  • Sort disjoint sublist: Edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sort stability: Fixed <pre> section, spacing, and edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sort using a custom comparator: Edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sorting algorithms/Bead sort: Changed the description from “Algorithm has O(S)…” to “The algorithm has O(S)…”, and edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sorting algorithms/Bogosort: Fixed <pre> section and edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sorting algorithms/Cocktail sort: Edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sorting algorithms/Comb sort: Edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sorting algorithms/Gnome sort: Edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sorting algorithms/Pancake sort: Added some spacing to the pseudocode and edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sorting algorithms/Shell sort: Edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sorting algorithms/Strand sort: Edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Soundex: Fixed list
  • Spiral matrix: Edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Split a character string based on change of character: Fixed <pre> section and edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • State name puzzle: Fixed links and edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Stream Merge: Edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Strip control codes and extended characters from a string: Removed a couple of redundant sentences. In the original challenge it’s a list, but here there would only be one item in that list that basically repeats the first sentence.
  • Sudoku: Edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Sum of a series: Added left margin to math functions
  • Sum to 100: Removed the word “Note”
  • Sutherland-Hodgman polygon clipping: Changed math functions to <pre> so users can scroll horizontally
  • Symmetric difference: Removed the word “Note” and edited the testString of the second test, changing it from “…should return a array” to “…should return an array”
  • Taxicab numbers: Added lists, bolded text, added left margin to taxicab number examples, added <code> tags to the 5th and 6th tests, and fixed grammatical error in instructions, chaging “it’s” to “its”
  • Tokenize a string with escaping: Added lists, <pre> section, and fixed spelling error, changing “quatro” to “cuatro”
  • Top rank per group: Added <code> tags and removed a commented out console.log call in the solution
  • Topological sort: Added list and fixed links
  • Towers of Hanoi: Fixed spacing in description and added spacing between arrays in the testStrings
  • Vector cross product: Fixed spacing in description and instructions, removed “i.e.” from the instructions, and changed the seed from function crossProduct() {... to function crossProduct(a, b) {... since the function should take two arrays as parameters
  • Vector dot product: Fixed spacing in description and instructions, removed “i.e.” from the instructions, and changed the seed from function dotProduct() {... to function dotProduct(...vectors) {... since the function should take any number of arrays as parameters
  • Word wrap: Fixed spacing in the description and instructions
  • Y combinator: Fixed spacing, bolded text, and added list.
  • Zeckendorf number representation: Fixed by @thecodingaviator in #35474
  • Zhang-Suen thinning algorithm: Fixed by @thecodingaviator in #35472
  • Zig-zag matrix: Fixed by @thecodingaviator in #35403

Duplicate challenges that have been skipped and will be removed in #35547:

  • Sorting algorithms - Bubble sort
  • Sorting algorithms - Counting sort
  • Sorting algorithms - Heapsort
  • Sorting algorithms - Insertion sort
  • Sorting algorithms - Merge sort
  • Sorting algorithms - Quicksort
  • Sorting algorithms - Radix sort
  • Sorting algorithms - Selection sort

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:19 (19 by maintainers)

github_iconTop GitHub Comments

1reaction
scissorsneedfoodtoocommented, Mar 2, 2019

@thecodingaviator, alright, sounds great! Thanks again for all your help here. I’ll review your PRs as they come in.

1reaction
thecodingaviatorcommented, Mar 1, 2019

@scissorsneedfoodtoo Alright! That’s how I’ll proceed with it now 👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

Rosetta Code/Count examples/Full list
Count Task ① ② ③ ④ ⑤ ⑥ ⑦ ⑧ ⑨ ⑩ 547 Hello world/Text ① ② ③ ④ ⑤ ⑥ ⑦ ⑧ ⑨...
Read more >
Category:Programming Tasks - Rosetta Code
Programming tasks are problems that may be solved through programming. When such a task is defined, Rosetta Code users are encouraged to ...
Read more >
Rosetta Code/Find unimplemented tasks
Task Given the name of a language on Rosetta Code, find all tasks which are not implemented in that language. Note: Implementations should...
Read more >
Rosetta Code:Add a Task
So you want to see a problem tackled, and you know enough about it that you can write a solution or two yourself....
Read more >
Rosetta Code:Village Pump/Suggest a programming task
So you want to see a problem solved? ... You also might want to check out the draft tasks to see if someone...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found