Skip to content
This repository has been archived by the owner on Oct 9, 2023. It is now read-only.

allow render_react_component(name, props, class: "...") #9

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

allow render_react_component(name, props, class: "...") #9

wants to merge 2 commits into from

Conversation

gfx
Copy link

@gfx gfx commented Dec 8, 2016

We need to specify HTML class attributes to the wrapper div elements.

Can you review it please?

BTW I can't pass the test (#8) so the CI will fail :(

Copy link
Collaborator

@ljharb ljharb left a comment

Choose a reason for hiding this comment

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

Can you elaborate on why you need this? Specifically, why does any code besides hypernova's clientside JS need to reference this div?

attributes = ''
options = job[:html_options]
if options && options[:class]
attributes << %{ class="#{options[:class]}"}
Copy link
Collaborator

Choose a reason for hiding this comment

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

what if options[:class] includes a double quote? please include a test case that covers this.

Copy link
Author

@gfx gfx Dec 8, 2016

Choose a reason for hiding this comment

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

How about cb90ed4 ?

@gfx
Copy link
Author

gfx commented Dec 8, 2016

Can you elaborate on why you need this? Specifically, why does any code besides hypernova's clientside JS need to reference this div?

This is because we need to apply CSS.

Out code includes CSS something like this:

foo {
  *[data-hypernova-key] {
     // blah blah blah
  }
}

This works but I think it is ugly and I don't want to depend on hypernova-specific things in CSS. If this PR is merged, I just add a CSS selector to the hypernova's div.

@ljharb
Copy link
Collaborator

ljharb commented Dec 8, 2016

@gfx what CSS are you trying to apply that can't be applied to the root element of your react tree?

@gfx
Copy link
Author

gfx commented Dec 9, 2016

Here you are:

  *[data-hypernova-key] {
    height: 100%;
  }

The height of a block element must be specified to the very element.

@ljharb
Copy link
Collaborator

ljharb commented Dec 9, 2016

To clarify, does this mean you're rendering the entire HTML content with react, and you want it to take up the whole screen?

@juanca
Copy link

juanca commented Jul 11, 2022

I have a couple of use-cases:

  1. Reduce unnecessary <div>s by styling the generated div instead of another wrapping <div>.
  2. Apply a grid area name to the container to make the generated div fit an area of the page (sub-grid feature is not yet supported)
  3. Apply a sticky position on either the generated div to make the react component sticky against the document.

Put it all together:

<body style="grid-template-areas: 'nav main'">
  <div style="grid-area: nav">
    <%= render_react_component('nav', { ... }, { style: "position: sticky; top: 0" }
  </div>
  <main>...</main>
  </div>
</body>

I could move the grid-area: nav to the generate div and make the react root component sticky. But either way, AFAIK, there is a necessity to style the generated div.

Unfortunately, I cannot render the whole application in React because our codebase is a mixture of accumulated tech stacks.

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