Skip to content

feat: complete util namespace tests #651

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

Simperfit
Copy link
Contributor

Q A
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets
License MIT
Doc PR

Add corverage to the Util Namespace

@Simperfit Simperfit force-pushed the feature/add-test-for-util-namespace branch from 340c087 to 37722b1 Compare July 31, 2016 09:03
@dunglas dunglas merged commit d24dbe4 into api-platform:master Jul 31, 2016
@dunglas dunglas deleted the feature/add-test-for-util-namespace branch July 31, 2016 13:47
@dunglas
Copy link
Member

dunglas commented Jul 31, 2016

Thanks Hamza!

@teohhanhui
Copy link
Contributor

Can we stick to the colloquial "foo", "bar", "baz" (at least prefer these first) for meaningless identifiers and strings please?

@dunglas
Copy link
Member

dunglas commented Aug 2, 2016

@teohhanhui we had the same debate several times for Symfony and I still don't get the why. Using funny (but still non discriminational) strings humanizes the project and has no drawback.

@teohhanhui
Copy link
Contributor

It's harder to parse mentally... 😄 Especially since "foo", "bar", "foobar" etc. are easily recognizable to most developers.

@Simperfit
Copy link
Contributor Author

I like to humanizes the project too, then I can say to people look, we added this in ApiPlatform, isn't it funny ? non-developers recognize that too ;).

magarzon pushed a commit to magarzon/core that referenced this pull request Feb 12, 2017
…or-util-namespace

feat: complete util namespace tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants