Blacklist repository is not a real yeoman-generator

[zckrs]

https://www.npmjs.com/package/generator-react-fullstack
If you check the code source the repository use yeoman only to copy
files of repository https://github.com/kriasoft/react-starter-kit

No choice in prompt, no repository on Github.
Strange publish @koistya

[addyosmani]

This looks like a legit case for blacklisting. I haven't personally landed blacklisting items recently so will defer to another member of the team.

[koistya]

No choice in prompt, no repository on Github.

@zckrs have you checked this branch - react-starter-kit/yeoman-generator? It is work in progress though, I'm working on adding prompts and stuff like that to make the yeoman template more customizable.

[zckrs]

It's a bit strange to reference yourself as a generator for a WIP feature in a branch.

[arthurvr]

If you check the code source the repository use yeoman only to copy
files of repository https://github.com/kriasoft/react-starter-kit

I honestly don't see much problems with a generator which just copies files. It's still more productive if you just need to run yo whatever to copy the files.

What does the rest think? I agree that the generator could use a bunch more features but I don't think this is strictly against our guidelines.

Do we even have explicit guidelines for what's a "valid" generator?

[SBoudrias]

This looks fine by me, plus the author came here to defend his project. As is, I see no reason to blacklist from our search results.

[zckrs]

The author came here to defend his project.

But the user who clicks on react-fullstack is redirected to https://github.com/kriasoft/react-starter-kit

[SBoudrias]

@koistya Could you fix the github link of your generator?

[koistya]

@SBoudrias yep, I will.

[arthurvr]

Thanks @koistya

[zckrs]

Still not updated 😞
Maybe we should add in blacklist then unblacklist when repository is fixed.

[koistya]

@zckrs if you look at the generator-react-fullstack NPM page, the repository URL is pointing to the right location there. I'm wondering, where does the yeoman.io site is picking repository URL from...

Well, if it's absolutely a must to have yeoman generator on the master branch in its own repo separately from the boilerplate project, I would move it to a separate repository, not sure how soon though.