Potential name confusion about autofixturejs

[kalebpederson]

Quite a while ago I looked for a version of AutoFixture for JavaScript and didn't find anything. Since nothing existed at that time, including this project, I wrote one that I wasn't permitted by work to Open Source at the time. My employer recently decided to allow us to open source certain things and so my implementation is now available on GitHub.

When designing it I purposefully made it very much like the C# implementation so it would be easier to learn, which you can see from the associated tests linked to above. Right now the API is quite similar but the backend is a bit different, in that I'm not keeping track of previous values, the numbers generated are more random, etc.

I'm in the process of cleaning it up, such as making it work with AMD, CJS, publishing to NPM, etc., but I'd like to avoid the naming conflict with this project yet still make it easy to find for individuals familiar with Mark's AutoFixture.

@ploeh and @jcteague, do you have suggestions on what you'd like to see happen? I have no objections to integrating into the AutoFixture organization as I intended it to be as similar as possible.

[moodmosaic]

AutoFixture has been around at least since Jan 29, 2010 and nowadays seems to be also known to Node.js users. A few days ago there was also a question on Twitter about AutoFixture in JavaScript.

@ploeh wrote:

Align the concepts and names etc. between the two projects.

IMHO, this is a great idea but also fairly big task.

It could be a lot easier if we first create a new JavaScript project in the AutoFixture GitHub organisation, set the foundations for the public JavaScript API and then try to re-use the existing functionality of this project – if possible.

That's primarily because AutoFixture is not exactly a random data generator. It encapsulates concepts from the xUnit Test Patterns book by Gerard Meszaros e.g. Equivalence Sets, deriving values drained from the aforementioned Sets generalized by the 80–20 rule, Custom Assertions, and more.

At the moment, I believe, and suggest friendly, that the easiest decision that will probably result to less confusion for the AutoFixture users, and this project's potential users, would be to find another name for this project.

[jcteague]

My appologies, I never received notice about this issue (something I'll see if I can remedy)

I'm familiar with Autofixture. I have no problems changing the name, but it's one of those things I and not very good at. Suggestions welcome.

[TheEvilDev]

I'm very interested in this project. I discovered it while searching for AutoFixture Javascript in the context of knowing about the .NET project (and loving it), and wanting something similar for js. While I understand AutoFixture.NET is much more than a data generator, for me, this was the core feature I need more than anything, and this project seems to fit that bill, and was easy to discover because of it's name.

If you could align the concepts and goals of the projects, that would be the ultimate. I can understand the concern over potential confusion for people working across the platforms, but I don't think this project is that far off the mark that if discovered by accident. Just my thoughts.

Look forward to playing with this library! Is there plans to release it on NPM?

[jcteague]

@TheEvilDev It is available on npm, but it might be a little out of date. I'm working on a node app again, so I'm sure there will be some activity here in the coming weeks.

[jcteague]

closing issue, since no has I don't have a better name