-
Notifications
You must be signed in to change notification settings - Fork 36
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
allow workbenches in BRJS libraries #950
Comments
By allowing libraries to have workbenches do we run the risk of the majority of coding moving to libraries, even when it's application specific? Is there anything we can do to guard against this happening? Or is this going to have to be something that falls under "good practice" and "culture"? |
Yes we do run that risk. The reason for putting code into libraries is to make it shareable and reuse it. Generally the more generic code becomes the more expensive it is to write. Code that is reused needs well defined use cases, a good API as well as copious documentation. |
Like Blades some libraries provide UI components so it would be useful to allow workbench(es) for BRJS libraries.
The text was updated successfully, but these errors were encountered: