https://github.com/bytekast/onprem-common-utils

https://github.com/bytekast/onprem-common-utils

Last synced: about 1 year ago
JSON representation

• Host: GitHub
• URL: https://github.com/bytekast/onprem-common-utils
• Owner: bytekast
• Created: 2015-11-10T04:16:14.000Z (over 10 years ago)
• Default Branch: feature-num2string
• Last Pushed: 2015-11-18T00:10:37.000Z (over 10 years ago)
• Last Synced: 2025-02-17T23:12:04.220Z (over 1 year ago)
• Language: Groovy
• Size: 6.84 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          

[![Build Status](https://travis-ci.org/bytekast/onprem-common-utils.svg)](https://travis-ci.org/bytekast/onprem-common-utils)

[![Coverage Status](https://coveralls.io/repos/bytekast/onprem-common-utils/badge.svg?branch=feature-num2string&service=github)](https://coveralls.io/github/bytekast/onprem-common-utils?branch=feature-num2string)

Number to String

================

Using your language of choice, produce a library that has the following capability within it:

**given some integer (N) as an argument, return a string representation of that integer.**

For example, using the capability in a scala REPL (implemented as a function called _int2str_) may look like this:

```

scala> int2str(5)

res0: String = five

scala> int2str(55)

res1: String = fifty-five

```

As a part of the submission, treat the library as though it were an API (which may have new capabilities in the future) that will be used within an organization for production use.  Given that, it should include an appropriate level of professional cleanliness that you would stand behind for a published library.

As far as the workflow for submission:

1. Create a branch, using a branch name you feel is appropriate.

2. Once you're satisfied with your solution, create a pull request against _master_