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

[TODO] Create a packaging toolkit for full-stack components #201

Open
Sing-Li opened this issue Nov 17, 2022 · 4 comments
Open

[TODO] Create a packaging toolkit for full-stack components #201

Sing-Li opened this issue Nov 17, 2022 · 4 comments

Comments

@Sing-Li
Copy link
Member

Sing-Li commented Nov 17, 2022

This is not a beginner task.

But if you have the right "stuff" you will recognize this as one of the most challenging and rewarding issue in this project. You're creating something here that doesn't exist (yet!). Anywhere!

Currently, the "full stack components" residing within this project are fully expanded and are subject to cross-talk pollution (devs working on one component mutating/using code from another).

Ideally, we want to have every component in its own repository - like npm modules, except "full stack". Devs should be able to create and share components for their own projects without notifying us. That is the only way that the component ecosystem can grow and thrive.

The pre-13 NextJS did not make this easy. NextJS 13 brings some componentization possibilities for SSR components (app). But our solution ideally shouldn't depend too much on this. We don't want to restrict the backend behaviors that are encapsulated in the components to NextJS only; we want it to include any and all microservices backend platforms as well as existing SaaS support APIs.

@Sing-Li Sing-Li changed the title [TO-DO] Create a packaging toolkit for full-stack components [TODO] Create a packaging toolkit for full-stack components Nov 17, 2022
@Palanikannan1437
Copy link
Contributor

Palanikannan1437 commented Nov 17, 2022

This is what I was waiting for!! I'd like to work on this for sure after the gitpod issue!!

It'd be awesome if you could assign this to me! Thank you!

@Sing-Li
Copy link
Member Author

Sing-Li commented Nov 18, 2022

This is not a small or short-duration project.

We have tried twice, unsuccessfully, for the past two years. Two failed multi-months attempts by very capable contributors.

Let's start a discussion here on the approaches / solutions first.

@Palanikannan1437
Copy link
Contributor

This is not a small or short-duration project.

We have tried twice, unsuccessfully, for the past two years. Two failed multi-months attempts by very capable contributors.

Let's start a discussion here on the approaches / solutions first.

Sure thing @Sing-Li 😇...I hope the poll component would lay off a foundation for this hopefully!!

@barelyhuman
Copy link

To start off so people can understand what it means,

can we lay down of what the minimal possible reproduction of this "full stack" component would be.

@Sing-Li

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

No branches or pull requests

3 participants