Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Should "base" be "common" #20

Open
slifty opened this issue Sep 27, 2020 · 0 comments
Open

Should "base" be "common" #20

slifty opened this issue Sep 27, 2020 · 0 comments
Labels
discussion The conversation is the point

Comments

@slifty
Copy link
Member

slifty commented Sep 27, 2020

Discussion

What do you want to talk about?

I wonder how intuitive the base name is, or if it should be something like common.

base might indicate that it's an entrypoint for the TV kitchen, whereas I suspect common indicates that the contents are common components across the project.

I'm not eager to make this kind of change since it would impact published packages but wanted to raise the concept.

If we did this I think we would want to deprecate the base version of the packages and eventually unpublish them so they're not sitting in our npm org any longer.

Relevant Resources / Research

None.

@slifty slifty added the discussion The conversation is the point label Sep 27, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
discussion The conversation is the point
Projects
None yet
Development

No branches or pull requests

1 participant