Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Mar 9, 2021. It is now read-only.

#37 multiline span on landing page in events card #58

Merged
merged 4 commits into from
Oct 25, 2017
Merged

#37 multiline span on landing page in events card #58

merged 4 commits into from
Oct 25, 2017

Conversation

abiduzz420
Copy link
Contributor

No description provided.

@abiduzz420 abiduzz420 changed the title #37 PR Request for multiline span on landing page in events card #37 multiline span on landing page in events card Oct 25, 2017
@coderplex-bot
Copy link
Collaborator

coderplex-bot commented Oct 25, 2017

Deploy preview ready!

Built with commit fc99f74

https://deploy-preview-58--coderplex.netlify.com

@M-ZubairAhmed M-ZubairAhmed self-requested a review October 25, 2017 11:18
Copy link

@M-ZubairAhmed M-ZubairAhmed left a comment

Choose a reason for hiding this comment

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

image
In events page we still want all three fields to be in the same line. Only in landing page they need to be in block.

@abiduzz420
Copy link
Contributor Author

I have added logic for selective multi-line using prop. For the RowEvent component on landing page, isMutliLine set to true is passed.

Copy link

@M-ZubairAhmed M-ZubairAhmed left a comment

Choose a reason for hiding this comment

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

Thank you for the improvement

  • Could you git checkout package.json and package-lock.json file, as changes to them are not required in this PR.
  • Also while checking for isMultiLine, please align items to left in index page row not in events as show below:
    image

@M-ZubairAhmed M-ZubairAhmed merged commit 4722e6c into coderplex-org:master Oct 25, 2017
@M-ZubairAhmed
Copy link

thanks thats great work. Please do checkout issues space from time to time.
Please start us to receive updates

@abiduzz420
Copy link
Contributor Author

abiduzz420 commented Oct 25, 2017

Formatting changes got included in the earlier commit for package.json and package-lock.json. I have not added any additional dependency. Thanks :) @M-ZubairAhmed. I will keep a check on the latest issues

@M-ZubairAhmed
Copy link

@abiduzz420 yes I have accepted, but its generally a good practice to only include the files which you have worked on in the pr.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants