+
Skip to content

Should we stay on one level methods per type or use some sugar style api? #33

@cusspvz

Description

@cusspvz

Sometimes we will face some methods that do just the same as other we have but with some difference on it, for those i'm thinking if we should place them on the same level or create sub ones.

Here is an example: we already have a method on Array type object called filter, which allows you to place a function to eval if a value should be filtered or not, inspite that we have also a method called randomFilter which does almost the same (filters array), but with a different propose.

My question here is if we should, on this cases, continue to apply one level for these methods (ƒ.Array.filter, ƒ.Array.randomFilter) or place similar methods inside of an existing one (ƒ.Array.filter, ƒ.Array.filter.random).

ping @gabrielpconceicao @brunocasanova @ajbloureiro

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载