ninja / ninjakit

Material Design for React

##Ninja the jQuery plugin for lethal interaction

###Develop

1.) Fork Ninja UI.

2.) Clone from your fork.

git clone [email protected]:$GITHUB_USER/ninja.git ~/Development

3.) Install dependencies:

cd ~/Development/ninja
npm install

4a.) Live reload/restyle your browser when libraries/tests change:

npm start

open http://localhost:3000/ for documentation or http://localhost:3000/test for tests

4b.) Or test manually:

npm test

5.) Commit your changes.

6.) Send a pull request.

###Authors uipoet and faisal

###License Copyright 2008-2012 Jamie Hoover.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.

You may obtain a copy of the License at

ninjaui.com/license.txt

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

ninjakit's Issues

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

[Bug]: Menu options appear beneath Dialog

Terms

• searched existing Issues

Describe the Problem

A Menu component (such as a ButtonMenu) within a Dialog will never display its options. This appears to be because the menu options themselves have no z-index, whereas the Dialog does.

It looks like a z-index is erroneously applied to the control that opens the menu, rather than the div which holds the options.

A mountpoint other than body, the default, can be specified, but in this case that seems like a workaround rather than the solution. Even within an arbitrary mountpoint, the menu options should appear above other contents.

Environment

No response

Web Browsers

No response

Operating Systems

No response

Logs

No response

[Feature]: Textarea component?

Terms

• searched existing Issues

Describe the Problem

Hello Jamie! Is there a component for multi-line text input? i.e., html "textarea" https://www.w3schools.com/tags/tag_textarea.asp ?

Thanks!

Propose a Solution

Add one in non exists?

Customizing Colors and Fonts

Hello. Can you draft the steps required to use some custom fonts and colors? Thanks

[Bug]: Typography doesnt support className / other intrinsic span attributes

Terms

• searched existing Issues

Describe the Problem

Getting a typescript error when adding className thought it works fine on the web page. Probably just a typing error.

Environment

No response

Web Browsers

No response

Operating Systems

No response

Logs

No response