should become [email protected] (tt) <[email protected]>, but becomes test test test org ([email protected] <[email protected]>) <[email protected]>

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• 🙋 Claim this issue: @sofiarivas

• 👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository

• 📝 Update the file README.md in the initials repository (press the little pen Icon) and edit the line as shown below.

  @@ -88,7 +88,7 @@ npm test
   Fine Print
   ----------
   
  -initials have been authored by [Gregor Martynus](https://github.com/gr2m),
  +initials has been authored by [Gregor Martynus](https://github.com/gr2m),
   proud member of the [Hoodie Community](http://hood.ie/).
   
   License: MIT

• 💾 Commit your changes

• 🔀 Start a Pull Request. There are two ways how you can start a pull request:

  1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
  2. You can edit files directly in your browser

• 🏁 Done Ask in comments for a review :)

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

For different names same initials appear. We need not just compare the Strings, but also the length of the name.

// scheme
['Moe Minutes', 'Moe Min'] -> ['MMi', 'MMi']

// test

  t.deepEqual(initials(['Moe Minutes', 'Moe Min'], 3), ['MMi', 'MMi'], 'not same name')
  t.deepEqual(initials(['Moe Minutes', 'Moe Mina'], 3), ['MMi', 'MoM'], 'not same name')

Start: function initialsForMultipleNames (names, options)

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 11.0.1 of standard was just published.

This version is covered by your current version range and after updating it in your project the build failed.

standard is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency semantic-release was updated from 15.13.32 to 15.14.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hello,

First off, thanks for sharing this project :)

I know that the project already says that the code is MIT licensed, but could you please also add a LICENSE file containing the text of the MIT license?

My understanding is that this may be necessary in order for the code to be considered legally licensed under MIT.

Babel recently went through something similar: babel/babel#7308

The devDependency tape was updated from 4.11.0 to 4.12.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 15.9.8 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 15.5.0 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency tape was updated from 4.12.0 to 4.12.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency browserify was updated from 16.3.0 to 16.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

browserify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency semantic-release was updated from 15.10.6 to 15.10.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I'd like to invite new contributors to this repository or open source in general to send a PR for this issue. Please let me know if you need any guidance, and if you want to give it a try, comment on the issue so others will now that it's taken.

You will need to install git & Node.js to work on this issue. Here are the steps you will need to set up the project locally, run the tests to see the problem, and fix it once you're done :)

1. Fork this repository, see http://guides.github.com/activities/forking/ for instructions
2. Clone it to your computer, see https://guides.github.com/activities/forking/#clone
3. Open the folder of the repository in your terminal
4. Run npm install
5. uncomment this test:

   initials/test/initials-test.js

   Line 43 in 906502d

   // t.deepEqual(initials(['Moe Minutes', 'Moe Min']), ['MoM', 'MMi'], '["Moe Minutes", "Moe Min"] ☛ ["MoM", "MMi"]')

6. Run npm test. You should see something like this:
7. Find a way to resolve the problem. Keep running npm test until all tests are green
8. Push your changes and start a Pull Request, see http://guides.github.com/activities/forking

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The devDependency semantic-release was updated from 15.13.27 to 15.13.28.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

As far as we have bootstrap-editable-table as bower dependency atm, I'd like to remove it and load bootstrap-editable-table via npm. Is this possible atm @gr2m?

https://github.com/gr2m/bootstrap-editable-table

Problem

Currently it has

type NameOrNames = string | string[];

function initials(nameOrNames: NameOrNames, options?: Options): string | string[];

which adds additional pain to the user who has to deal with the fact that

const myInitials: string = initials('John Doe');

won't compile, besides documentation explicitly saying that the result will be JD (i.e. string).

Possible way to improve typings

type NameOrNames = string | string[];

function initials<T extends NameOrNames>(nameOrNames: T, options?: Options): T;

In this case if array is passed as a first argument, then function returns an array. And if it's just a string then its return type also is just a string.

Version 4.9.1 of tape was just published.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

currently is Fr nk d (Fnd)

after cloning the repositories, install dependencies with npm install and then run npm run test:coverage. That will create the coverage/lcov-report/ folder. Open coverage/lcov-report/index.html to see what lines / branches are not yet covered

Hi @gr2m, thank you for open-sourcing this library!

I noticed when I pass in a single word, it returns the first two letters of that name as the initial. That too me felt counter-intuitive, since initials tend to be the first letter from each word. I wonder if the behavior should accomodate for providing just one letter (either by default or as a param) per word - in which case if someone passed in "Github", it would return just "G".

Thoughts?

The devDependency semantic-release was updated from 15.13.20 to 15.13.21.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Is it possible to limit initials to two characters? while maintaining the "uniqueness", of course until all permutations exhausted.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Jan-Erik doesn't get an initial.
Do we treat this as a bug @gr2m?

The devDependency semantic-release was updated from 16.0.0 to 16.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency rimraf was updated from 2.6.3 to 2.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rimraf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 15.9.15 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Are there any plans to add TypeScript support?

The devDependency semantic-release was updated from 15.13.28 to 15.13.29.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

• move index.html into /demo folder
• make initials.js commonjs-only, just one module.exports = initials, without checking for define, and the wrapper functions anymore. Rename file to index.js and make it the "main" in package.json
• add a local dev server that serves /demo and dynamically browserifies initials and serves it at /initials.js. beefy could be a simple option for that, the npm start task could look like beefy ./index.js --cwd=./demo
• add a build task, build into /dist. Add /dist to gitignore
• Add .npmignore (only coverage/ in it, so that /dist gets added to published pacakge)
• Add deploy task, which is 1. build, 2. copy build initials.js file to /demo, 3. gh-pages-deploy of /demo folder
• remove the release.branch setting in package.json
• remove branches setting in .travis.yml

That should be it :) @zoepage want to give this a go? Does it all make sense?

@gr2m
Is it possible to move the initials.js to a specs folder or would it break something?
I'd love to add a cleaned up structure for all the modules.

Version 15.4.3 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

First off, thanks for putting this library together! I noticed this error while developing today:

node_modules/initials/index.d.ts:20:2 - error TS2309: An export assignment cannot be used in a module with other exported elements.

  export = initials;
  ~~~~~~~~~~~~~~~~~~

Changing this line to export default initials fixes the error.

TypeScript version: 3.9.5
initials version: 3.1.0

I'm happy to open a follow-up pull request.

Emojis ends up as an illegal character:

t.equal(initials('John 🐐face'), 'J🐐', 'John 🐐face (j🐐) ☛ j🐐');

✖ John 🐐face (j🐐) ☛ j🐐
    --------------------------
      operator: equal
      expected: 'J🐐'
      actual:   'J�'
      stack: |-

The devDependency tape was updated from 4.12.1 to 4.13.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

use case: multiple fields that might contain the same names. Example:

1. Project owner: 'John Doe'
2. Assigned: 'John Doe, Jane Dane'

In that case I'd like initials for 'John Doe' to be 'JD', and for 'John Doe, Jane Dane' to be 'JD, JDa' instead of 'JDo, JDa'

suggested API:

// pass existing initials for names
initials(['John Doe', 'Jane Dane'], {
  existing: { 'John Doe': 'JD' }
})
// ['JD', 'JDa']

interestingly, initials.addTo('안형준') works as expected.