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

feat: add ContentSlot component #1014

Merged
merged 2 commits into from
Jan 21, 2024
Merged

feat: add ContentSlot component #1014

merged 2 commits into from
Jan 21, 2024

Conversation

alissawix
Copy link
Contributor

add a ContentSlot component which will be used in boards to wrap the actual content(s) of the board.
usually a componnet

@@ -33,6 +33,27 @@ createBoard({
});
```

You can also create boards with separation between the actual content and the board environment.
Copy link
Contributor

@alisey alisey Jan 17, 2024

Choose a reason for hiding this comment

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

This doesn't explain the motivation for <ContentSlot />. So for the time being, while this component has no practical use, I wouldn't even introduce it in the readme, and keep as undocumented feature.

Once Codux supports it, I would add the real explanation.

Copy link
Contributor Author

@alissawix alissawix Jan 17, 2024

Choose a reason for hiding this comment

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

the docs for the createBoard also don't really explain :)
the real docs should be in codux

so remove the entry from readme?

Copy link
Contributor

@alisey alisey Jan 17, 2024

Choose a reason for hiding this comment

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

so remove the entry from readme?

Yeah, or change the comment. Because someone who isn't aware of our future plans will not understand what's the point of creating "separation between the actual content and the board environment".

We could add something like:

When the board is converted to a code snippet, only the children of the <ContentSlot> will be included into the snippet. This is useful when the board is wrapped in a router or a context provider that shouldn't be included in the snippet.

This doesn't explain the idea of converting the board to a code snippet, but whatever.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added to the readme

when the feature is done we will have a whole lot of docs in the Codux docs

@barak007
Copy link

why do we need this?

@alissawix alissawix merged commit d324055 into master Jan 21, 2024
6 checks passed
@alissawix alissawix deleted the alissav/add-content-slot branch January 21, 2024 13:48
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.

3 participants