Skip to content

Update README.md - Change the import #1

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.

Sign up for GitHub

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

Open
SveeJ wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md - Change the import #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The adapter is a direct stateless interface with Challonge, with no frills, you'
### Example - Retrieving a list of tournaments with the TournamentAdapter
The following returns the direct raw response from the Challonge API
```
import { TournamentAdapter } from 'challonge-ts';
import { TournamentAdapter } from '@nuel/challonge-ts';

const test = async () => {
const data = await TournamentAdapter.index('api_key');
Expand All @@ -28,7 +28,7 @@ Devised as a nicer abstraction over the adapter, this is a set of classes which
### Example - Retrieving a list of tournaments with the Challonge class

```
import { Challonge } from 'challonge-ts';
import { Challonge } from '@nuel/challonge-ts';

const test = async () => {
const challonge = new Challonge('api_key')
Expand All @@ -52,4 +52,4 @@ To regenerate the API nock files, delete the `tests/adapter/__nock-fixtures__` f
Ensure you have `gulp-cli` installed locally, then run `npm run build`. Hopefully it goes all right with no errors! :)

## Merging with master
After you have run the tests, and built the project, your repo should be good to go for merging with master!
After you have run the tests, and built the project, your repo should be good to go for merging with master!