Skip to content
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

remove unused app.name #899

Merged
merged 1 commit into from
Feb 18, 2017
Merged

remove unused app.name #899

merged 1 commit into from
Feb 18, 2017

Conversation

amitport
Copy link
Contributor

app.name is mentioned in the documentation, but doesn't seem to have any semantic meaning.

Application instances are not frozen and as far as I can tell there's no reason to force people to use name specifically (people may want to use id / machineId, etc., or even better, don't rely on koa app's namespace to pass this information)

@codecov
Copy link

codecov bot commented Feb 13, 2017

Codecov Report

Merging #899 into v2.x will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##           v2.x   #899   +/-   ##
===================================
  Coverage   100%   100%           
===================================
  Files         4      4           
  Lines       421    421           
  Branches    100    100           
===================================
  Hits        421    421

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d48291f...92e3432. Read the comment docs.

@@ -110,7 +110,6 @@ app.listen(3000);
Application settings are properties on the `app` instance, currently
the following are supported:

- `app.name` optionally give your application a name
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the convention might already been established. What is the point of removing it?

@amitport
Copy link
Contributor Author

a minimal interface better
-> less potential for confusion/forward-incompatibility-issues/pointless-discussions
-> seem to be the general philosophy with koa (which I like)
-> that being said, if it is indeed 'already been established', probably no need to remove it

@jonathanong
Copy link
Member

👍 for this. anyone else?

@tj
Copy link
Member

tj commented Feb 18, 2017

👍 I don't remember what it's for haha

@jonathanong jonathanong merged commit 00156df into koajs:v2.x Feb 18, 2017
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.

None yet

4 participants