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

[FEATURE]: Neutered View #136

Open
hirokazutei opened this issue Jan 24, 2021 · 0 comments
Open

[FEATURE]: Neutered View #136

hirokazutei opened this issue Jan 24, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request flow flowtype good first issue Good for newcomers ts

Comments

@hirokazutei
Copy link
Owner

So, given that Inset takes some responsibilities away from View, it still does not stop users from using View to achieve what Inset is meant to do. What if we use the configuration that we apply to Inset and takes that to create a View that is "neutered" so that some concerns that Inset is meant to take are removed from View (like padding, margin, etc,).

There are going to likely be some overlaps since cleanly separating View into Inset and NeuteredView (I need a better name) would probably prove to be inconvenient.

@hirokazutei hirokazutei added the bug Something isn't working label Jan 24, 2021
@hirokazutei hirokazutei self-assigned this Jan 24, 2021
@hirokazutei hirokazutei added enhancement New feature or request flow flowtype good first issue Good for newcomers ts and removed bug Something isn't working labels Jan 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request flow flowtype good first issue Good for newcomers ts
Projects
None yet
Development

No branches or pull requests

1 participant