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

OBPIH-826: New template for upcoming shipment feature. #268

Merged
merged 2 commits into from
Apr 26, 2018
Merged

Conversation

awalkowiak
Copy link
Collaborator

@jmiranda jmiranda added the status: work in progress For issues or pull requests that are in progress but not yet completed label Apr 26, 2018
@awalkowiak awalkowiak assigned jmiranda and pmuchowski and unassigned jmiranda and pmuchowski Apr 26, 2018
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="layout" content="custom" />
Copy link
Contributor

Choose a reason for hiding this comment

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

you could link bundle.css here:
<link rel="stylesheet" href="${createLinkTo(dir:'css/', file:'bundle.css')}">

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I forgot about it :D

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="layout" content="custom" />
Copy link
Member

Choose a reason for hiding this comment

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

Using the "custom" template might become problematic for you guys since it includes all of the old JS and CSS resources used on the existing pages. Use the main.gsp layout instead. Customize it to your needs and remove whatever doesn't need to be there. For example I think I saw a navbar item with the label "test" -- oops.
<meta name="layout" content="main" />

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I used "custom" layout, because i wanted to have current menu integrated with upcomming features. At this point it is looking ok (we have current menu and our react component in body) . If you want, then i can use main layout there and add something similar to analytics navbar.

Copy link
Member

@jmiranda jmiranda Apr 26, 2018

Choose a reason for hiding this comment

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

It's ok for now. We can work on getting main.gsp in shape for the feature in another ticket. My point was just that you'll start to see the YUI CSS and other CSS bleeding into the page as you start to add your react components. So your bootstrap components won't look exactly like you expect.

Copy link
Collaborator Author

@awalkowiak awalkowiak Apr 26, 2018

Choose a reason for hiding this comment

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

I think it would be better to have a new task for this. Right now i could quickly swap layout to main and clean up it completely (it would have just body with our react component)

Copy link
Member

Choose a reason for hiding this comment

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

Sounds good. Stay with custom and I'll create a new ticket for the main layout.

@jmiranda jmiranda merged commit e90e0c4 into develop Apr 26, 2018
@jmiranda jmiranda deleted the OBPIH-826 branch April 26, 2018 16:57
@jmiranda jmiranda removed the status: work in progress For issues or pull requests that are in progress but not yet completed label Apr 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants