-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
[NEW] REST API endpoint /directory
#10442
Conversation
}); | ||
}); | ||
|
||
describe('/settings.oauth', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be moved to the settings one and not the miscellaneous one? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops.. looks it's duplicated of this one.
@MarcosSpessatto can you please remove this test from here?
}); | ||
}); | ||
|
||
describe('/settings.oauth', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops.. looks it's duplicated of this one.
@MarcosSpessatto can you please remove this test from here?
limit: count | ||
})); | ||
|
||
if (result) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think as a good practice, the unexpected condition should be treated specially and not the successful one.
so I will ask you to change this here, so the if
will trigger the failure.
looks like addressed feedback
/directory
@rodrigok did you test this yourself? We were investigating an issue with the rest API not working on the deployed heroku instance. |
@graywolf336 the last instance I tried on heroku was built based on |
Well it had the |
Add REST /directory endpoint.
Closes #9961.