GithubHelp home page GithubHelp logo

nkkollaw / zubr Goto Github PK

View Code? Open in Web Editor NEW
99.0 7.0 6.0 152 KB

Wrapper library to fix inconsistencies in PHP's core functions

License: MIT License

PHP 98.62% Shell 1.38%
php php-7 php-library php-functions functions-beautifier wrapper conventions

zubr's Introduction

Zubr

Wrapper library to fix inconsistencies in PHP's core functions

PHP is great and Composer, PHP-FIG, and all the different frameworks make it even greater. However, there is still legacy stuff in the language itself that makes PHP harder to use than it should be (see http://phpsadness.com/ for one of many lists).

Zubr is a wrapper library to fix inconsistencies in PHP's core functions. It wraps PHP's built-in functions and attempts to fix a few things—starting with consistent naming, order of arguments, and more.

For instance, from:

parse_url()
urlencode()

to:

\Zubr\parse_url()
\Zubr\url_encode()

and even:

htmlentities()
html_entity_decode()

to:

\Zubr\html_entity_encode() // alias to htmlentities(), \Zubr\html_entities()
\Zubr\html_entity_decode()

Functions always have the same name as the built-in ones, but they follow the same set of rules. Zubr is intuitive to use, because function names are predictable and similar to the ones you're used to.

Zubr's idea came from commenting this HN post: https://news.ycombinator.com/item?id=14883784

Rules

0. Introduction

We're ignoring PHP < 7.0.0. Any function that is deprecated and not included in PHP 7.0.0 won't be found in Zubr.

1. Function naming

1.1 Underscores

See: http://phpsadness.com/sad/4

We always use snake_case.

1.2 Prefixes

See: http://phpsadness.com/sad/15

We add aliases using micro instead of u (which sometimes means user).

We add aliases using user instead of u (which sometimes means micro).

1.3 to vs. 2

See: http://phpsadness.com/sad/48

We add aliases using to instead of 2.

2. Order of arguments

2.1 Needle/haystack

See: http://phpsadness.com/sad/9 and similar.

We always put the subject first, then the keyword ($haystack first, then $needle).

For example, you'd say "search Google for dog" (which means "search $subject for $keyword").

Most PHP functions already follow this convention.

2.2 Callbacks

See: http://phpsadness.com/sad/6

We always put the callback last.

3. Argument type

Note: If the parameters given to a function are not what it expects, such as passing an array where a string is expected, the return value of the function is undefined. In this case it will likely return NULL but this is just a convention, and cannot be relied upon. http://php.net/manual/en/functions.internal.php

We'd like to fix the above in > 1.0 releases.

Roadmap

Version 1.0 will contain all of PHP's core built-in functions.

We might then go on to implement a private plugin system to add bundled extensions in 2.0, and make the plugin system public so that anyone can implement wrappers to external extensions in version 3.0.

We have detailed milestones with all features that will be implemented up to version 1.0 at https://github.com/nkkollaw/zubr/milestones.

Contribute

Pull requests are welcome.

Take a look at the CONTRIBUTING.md file.

Contact us

Emails can be found in the composer.json file.

zubr's People

Contributors

brzuchal avatar ddziaduch avatar nkkollaw avatar radmen avatar tommica avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

zubr's Issues

Fix parameter order

Parameters should follow the following rule:

Always 'subject', then 'keyword' (for example you'd say "search Google (%SUBJECT%) for %KEYWORD%").

That is, $haystack first, then $needle.

No name?

Although the namespace should IMHO be called PHP for clarity and readability, I think the project should have a somewhat recognizable name/repo name.

Even something like PHP-sane or PHP-wrapper.

Opinions..?

No tests?

I know that this library may be considered "just" a wrapper. Yet the lack of tests disturbs me a little.

Should they be included?

Guidelines are incomplete

IMO, we need to set the project's scope/objectives, and guidelines on every issue.

I added what I was personally interested in in the README: parameter order, underscores, etc. Guidelines could be moved to a dedicated file or the wiki as that would keep things more organized.

What problems do we tackle? Function naming for sure, but what about inconsistent errors? There might be more things that we can "fix".

Workflow

To get to version 1.0, we have to add all functions that a default PHP installation comes with (we'll think about extensions in the future, perhaps via a plugin system).

The most comprehensive list I could find is this: http://php.net/manual/en/extensions.membership.php

We would have to support all functions under "Core" (http://php.net/manual/en/extensions.membership.php#extensions.membership.core), and "Bundled" (http://php.net/manual/en/extensions.membership.php#extensions.membership.bundled).

I'm adding each function as an issue, so that whoever implements it can reference the issue while committing or doing pull requests.

I think we should do 1 function per commit/request, referencing the issue.

Would this work in your opinion?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.