infinitered / ignite-dev-screens

Ignite DevScreens plugin for ignite-cli

Ignite Dev Screens

Why is this archived?

We really appreciate all the community support in the years since we first released ignite-dev-screens. Our focus has shifted to the latest version of Ignite, which does not have a plugin-based architecture (read more here). Feel free to fork this library and continue on its legacy if you want.

This npm packages contains the development screens for Ignite generated projects.

Usage

Generate an Ignite project and then add this plugin:

$ ignite add dev-screens

What it does

When you add this plugin to your Ignite project, some files will be added to ignite/DevScreens. These contain some styled utility screens where you can view components, play with various Ignite features, and add your own components during development.

To remove Ignite DevScreens from your project, just delete ignite/DevScreens.

Troubleshooting

If you're having an issue with Ignite DevScreens, either file an issue here or chat with other mobile engineers in our community Slack team.

License

The MIT License (MIT), copyright (c) 2017 Infinite Red, Inc.

ignite-dev-screens's Issues

Fix yellowboxes

Currently using two deprecated methods in NetInfo which cause yellowboxes.

Move to equivalent (and tested) alternatives.

Remove block padding to pass Standard 10.0.2 linting rules

/Users/robinheinze/Code/ir/internal/playground/is5/ignite/DevScreens/APITestingScreen.js
  94:41  error  Block must not be padded by blank lines  padded-blocks

/Users/robinheinze/Code/ir/internal/playground/is5/ignite/DevScreens/PresentationScreen.js
  17:50  error  Block must not be padded by blank lines  padded-blocks

/Users/robinheinze/Code/ir/internal/playground/is5/ignite/DevScreens/ThemeScreen.js
  16:58  error  Block must not be padded by blank lines  padded-blocks

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Dev screens breaks boilerplate

Issue is described in infinitered/ignite#1061. Basically a Bowser generated ignite including dev screens breaks when launching in development mode:

undefined is not an object (evaluating 'RNDeviceInfo.systemManufacturer')

package.json already includes dep ignite-dev-screen and react-native-device-info.

I manually fixed it with react-native link react-native-device-info.