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

Documentation for requireLogin Class #4509

Closed
SidharthBansal opened this issue Jan 3, 2019 · 11 comments · Fixed by #4576
Closed

Documentation for requireLogin Class #4509

SidharthBansal opened this issue Jan 3, 2019 · 11 comments · Fixed by #4576
Assignees
Labels
documentation feature lacks proper documentation or needs more documents help wanted requires help by anyone willing to contribute

Comments

@SidharthBansal
Copy link
Member

SidharthBansal commented Jan 3, 2019

Part of #4132.
Add documentation for the new requireLogin class so that we can add that to the new buttons etc in future as per Jeff's suggestion #4132 (comment).

@SidharthBansal SidharthBansal added fto-candidate issues which are meant to be solved by first timers but aren't well-formatted yet documentation feature lacks proper documentation or needs more documents labels Jan 3, 2019
@SidharthBansal SidharthBansal added this to the Login/SignUp & OAuth milestone Jan 3, 2019
@SidharthBansal SidharthBansal removed the fto-candidate issues which are meant to be solved by first timers but aren't well-formatted yet label Jan 3, 2019
@grvsachdeva grvsachdeva added the help wanted requires help by anyone willing to contribute label Jan 4, 2019
@SidharthBansal
Copy link
Member Author

@oorjitchowdhary are you willing to write this piece of documentation. This will be your first part to write the documentation. Documentation helps in using the function in future.

@SidharthBansal
Copy link
Member Author

This is really close to the work which you did in last couple of weeks.

@oorjitchowdhary
Copy link
Member

Hi @SidharthBansal .. Yes I'll do this one..
Where should I add the documentation and how long should it be... 2-3 lines or more?

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Jan 7, 2019 via email

@oorjitchowdhary
Copy link
Member

oorjitchowdhary commented Jan 7, 2019

I don't think readme will be appropriate place. Any suggestions?

Yes, I don't think we should put it in the README.. I think it'll be best to create a new file for Login and Signup functionalities just like there is EMAIL.md in /doc

This doc could focus on the login and signup modals we created.. and the use of login and signup pages even after the modals.. and also the requireLogin class

But I'm confused what will we name this file... LOGIN.md or SIGNUP.md won't work as this will comprise of both of them

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Jan 8, 2019 via email

@jywarren
Copy link
Member

jywarren commented Jan 8, 2019 via email

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Jan 8, 2019 via email

@oorjitchowdhary
Copy link
Member

So should I make a new file as LOGIN_SYSTEMS.md or change OMNIAUTH.md to LOGIN_SYSTEMS.md??

@jywarren
Copy link
Member

jywarren commented Jan 8, 2019 via email

@ghost ghost assigned oorjitchowdhary Jan 8, 2019
@ghost ghost added the in progress label Jan 8, 2019
@SidharthBansal
Copy link
Member Author

SidharthBansal commented Jan 9, 2019 via email

@ghost ghost removed the in progress label Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation feature lacks proper documentation or needs more documents help wanted requires help by anyone willing to contribute
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants