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

Headings created #855

Merged
merged 6 commits into from Mar 17, 2018
Merged

Headings created #855

merged 6 commits into from Mar 17, 2018

Conversation

asquare14
Copy link
Member

issue #846 resolved.
Created Headings .

@asquare14 asquare14 requested a review from nshki March 16, 2018 02:19
import css from './Heading.scss';

type Props = {
large?: boolean,
Copy link
Member

Choose a reason for hiding this comment

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

Should all these fields be mandatory rather than optional?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think mandatory as then user can use whatever he requires based on props passed. @nshki What are your views on this ?

Copy link
Member

Choose a reason for hiding this comment

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

I think it makes sense to make the label prop mandatory, but the rest can stay optional.

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't know how to make them optional. What do I have to do ?

Copy link
Member

Choose a reason for hiding this comment

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

You used ? so that should be enough :)

Copy link
Member Author

Choose a reason for hiding this comment

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

Okay :)

nshki
nshki previously requested changes Mar 16, 2018
Copy link
Member

@nshki nshki left a comment

Choose a reason for hiding this comment

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

Overall looks good! Just a couple comments.

import css from './Heading.scss';

type Props = {
large?: boolean,
Copy link
Member

Choose a reason for hiding this comment

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

I think it makes sense to make the label prop mandatory, but the rest can stay optional.

return (
<span>
<div className={labelClassNames}>{label}</div>
</span>
Copy link
Member

Choose a reason for hiding this comment

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

Instead of having two layers of elements, let's just keep it at one. I think a heading element would make sense here!

Copy link
Member Author

Choose a reason for hiding this comment

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

Which headings should I use. I am thinking
h1 - for large
h2 - for normal
h3- for small
h4- for text

Copy link
Member

Choose a reason for hiding this comment

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

I personally think we should be using divs that way if we change the hierarchy of headings we don't need to refactor all of H level headings. I think a div without a parent span should be enough!

Copy link
Member Author

Choose a reason for hiding this comment

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

okay ! Cool !

@asquare14
Copy link
Member Author

@julianguyen Why are the tests failing ? It is showing Rspec problem. How do I fix it ?

@julianguyen
Copy link
Member

Looks like flakey tests. Argh. I'll look for a way this weekend to reduce the flakiness. Sorry about that!

@asquare14
Copy link
Member Author

Okay ! :)

julianguyen
julianguyen previously approved these changes Mar 17, 2018
Copy link
Member

@julianguyen julianguyen left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks so much for working on this and doing an awesome job as always 💜

@asquare14
Copy link
Member Author

Thanks a lot @julianguyen ! Your kind words keep me and Prateksha motivated ❤️ I'll merge it after the tests ?

@julianguyen
Copy link
Member

Yep yep! It should go green 🍀

@asquare14
Copy link
Member Author

asquare14 commented Mar 17, 2018

@julianguyen Could you trigger it again ? Tests failed. I do not have write permissions and hence cant trigger it !

@julianguyen
Copy link
Member

Looks like there are legitimate issues this time around. Scroll down the page to where the red box is highlighted for more details! Let me know if you need help. I'll be away from internet for an hour or so though.

@asquare14
Copy link
Member Author

@julianguyen Can you please approve again ? The tests finally passed :)

@asquare14 asquare14 dismissed nshki’s stale review March 17, 2018 05:18

Okay it's already done :)

@asquare14 asquare14 merged commit 928a6ed into ifmeorg:master Mar 17, 2018
@asquare14 asquare14 deleted the heading branch March 18, 2018 06:17
@prateksha prateksha added the RGSoC 2018 Rails Girls Summer of Code 2018 label May 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RGSoC 2018 Rails Girls Summer of Code 2018
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants