-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Site editor sidebar: extract get page details function. #51038
Conversation
Size Change: 0 B Total Size: 1.39 MB ℹ️ View Unchanged
|
This is testing well for me 👍 From the linked discussion, it sounds like the feedback from @ntsekouras was about storing the details within the top level component. This PR appears to still store the details in the parent component, but with the logic moved to another file. In principle, this sounds good to me, but the structure of the props involves a couple of names that are particular to I think if the function is remaining the same, I'd slightly lean toward either keeping the function where it is, since it's coupled quite tightly to the implementation in What do you think? |
To be honest, I wasn't too clear about that feedback and probably misinterpreted it. @ntsekouras could you elaborate (assuming you think it's still needed).
Makes total sense. I'll close this PR since it's not affecting functionality at all. |
That was my comment about, yes. Since the component is not used elsewhere yet and we haven't seen if the current UI component abstraction( Since it's not public API, we can explore and revisit while implementing the other use cases, and act accordingly. Thanks for the PR though Ramon! |
Good point. I'll revisit whether we need it in a follow up tomorrow. Thanks again! |
What?
Extracting
getPageDetails
function into a separate file.Context: #50767 (comment)
Why?
Organizational bliss.
Testing Instructions