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

Created adapter blueprint with db name in config environment #91

Closed
wants to merge 10 commits into from

Conversation

mattmarcum
Copy link
Contributor

I saw in the dummy app adapter that you had a TODO to grab the db name from some external source. I think this is the community's preferred method is sticking this stuff in the config. I went ahead and created an adapter blueprint to match what's in the readme and to pull in the db name from the config.

@mattmarcum mattmarcum changed the title adapter blueprint with db name in config environment Created adapter blueprint with db name in config environment Sep 6, 2015
@@ -0,0 +1,32 @@
import { Adapter } from 'ember-pouch/index';
Copy link
Collaborator

Choose a reason for hiding this comment

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

you don't need index: import { Adapter } from 'ember-pouch';

@fsmanuel
Copy link
Collaborator

fsmanuel commented Sep 6, 2015

👍

@mattmarcum
Copy link
Contributor Author

Thanks for the code review, fixed those issues.

@rsutphin
Copy link
Collaborator

rsutphin commented Dec 5, 2015

I think this is a good idea. I think it would be more in keeping with Ember style for the config key to be camelized (emberPouch). Otherwise I think this is a good idea.

Sorry again for the slow response.

live: true,
retry: true
});
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

This block is double-indented (4 spaces instead of 2).

@mattmarcum
Copy link
Contributor Author

Ok updated the key and added a section to the README

@rsutphin
Copy link
Collaborator

Great, thanks. If you could rebase & squash we'll be ready to merge.

@mattmarcum
Copy link
Contributor Author

closing in favor of #102

@mattmarcum mattmarcum closed this Dec 19, 2015
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