konkked / underscore.cs Goto Github PK

Currently, the unit tests in Underscore.Tests are outdated and using an uninformative and often unnecessarily verbose async format. These tests should be cleaned up and refactored to use the new standard for this projects tests, which needs to be specified as another issue.

Create tests for the util module

The tests in Object need to be updated to match the new testing guidelines at /docs/Coding Standards.md. This should be done in tandem with #15

The tests in Action need to be updated to match the new testing guidelines at /docs/Coding Standards.md. This should be done in tandem with #11

The Collection API needs a doc with detailed descriptions and examples, to be put in /docs/api with the other API docs.

Need to create some documentation to make the library more user friendly

A lot of what underscore does is manipulating lists of items, this project could be an incredible powerhouse if it works as an extension to LINQ as to acting on list, arrays and other enumerable types.

The tests in Function need to be updated to match the new testing guidelines at /docs/Coding Standards.md. This should be done in tandem with #13

If you take a look at the unit tests can see that the debounce and throttle test fail sometimes but not others, they do not fail by a large amount (usually one or two off) but still would be best to figure out what is going on and try to find a better solution

There's no need to have List exposed externally, since it's exposing implementation details that aren't important to the consumer. Instead, consumers should just use Collection equivalents and if there's a relevant optimization the library will switch to it internally.

doesn't do what someone would expect if the object ( use methods provided by IEquatable to check for equality ) should change the name to something else...

Suggestions?

Think _.Object.SoftEquals(a,b) might be okay, not sure if "Soft Equals" is exactly clear.

Throttle has been acting funny, it is hard to pinpoint why because the code is expected to be run async both on a single thread and across multiple ones.

Would also like more tests to be run on Debounce as I have only been able to test it on one computer, would be helpful to test in different environments

Should we be commenting for Intellisense on everything? Even if it is not meant to be publically accessible?

We can do it but just takes a lot of time.

Maybe we can come up with a script or something that puts comments in the signature of methods that implement an interface?

Feel like there has to be a better way to work around having to basically repeat all my code everywhere for debounce and throttle, basically repeating code all over the place.

in code documentation still needs to be written

The Utility API needs a doc with detailed descriptions and examples, to be put in /docs/api with the other API docs.

Create a more complete set of tests for Object.Constructor module

Need to update home page to reflect the changes made

Not sure how to test the threading component but still would like to come up with some organized tests if possible

It may be Asinine, but .Select is not clear that it can (and often is) used as a Map function.

Additionally, Aggregate is a little clearer that it's a reducing function but is not using the same naming convention as Underscore "reduce"

Together both of these APIs will make developers who go from JavaScript Underscore -> C# Underscore a little more seamless.

the Debounce will run many time for every internal time, it's not correct.

Maybe you can follow this repository https://github.com/zpbappi/underscore-net, it has correct behavior.

Doing some weird stuff in Object reflection class Members, should probably refactor to be less bizarre

The tests in List need to be updated to match the new testing guidelines at /docs/Coding Standards.md. This should be done in tandem with #14

Since we moved all the tests to be using the actual _ instance doesn't make sense to have empty constructors, should remove them

The List API needs a doc with detailed descriptions and examples, to be put in /docs/api with the other API docs.

Documentation needed for Object.Method ( docs )

Documentation needed for Object.Property ( docs )

The tests in Collection need to be updated to match the new testing guidelines at /docs/Coding Standards.md. This should be done in tandem with #12

Hi, I would like to use Underscore.cs to generate html content, just like in Underscore.js way below

_.templateSettings.variable = "rc";

in html file, I can access listTitle associated with rc variable.

    <h2>
        <%- rc.listTitle %>
    </h2>

More information, please check
http://www.bennadel.com/blog/2411-using-underscore-js-templates-to-render-html-partials.htm

Does Underscore.cs support this kind of usage now?

The tests in the project should be converted to make transitioning to .NET Core easier.

The testing standards need to be written down for the sake of consistency in naming conventions and how to handle testing edge cases.

The Object API needs a doc with detailed descriptions and examples, to be put in /docs/api with the other API docs.

The tests in Utility need to be updated to match the new testing guidelines at /docs/Coding Standards.md. This should be done in tandem with #16

The Action API needs a doc with detailed descriptions and examples, to be put in /docs/api with the other API docs.

List.DelegateComponent should have List.Delegate removed because it has no practical use cases, and there should be a Definition/Implementation added to Collection for resolve so that it can be used once list is hid as part of #17.

The Function API needs a doc with detailed descriptions and examples, to be put in /docs/api with the other API docs (combine with Action?).

Create a more complete set of tests for Object.Attribute module