native-ly / marginally-pudding Goto Github PK

🍮 Create margins and paddings in React Native in the way well known from CSS

Home Page: https://snack.expo.io/@jbiesiada/marginally-pudding

License: MIT License

JavaScript 19.35% TypeScript 79.49% Shell 1.16%

react react-native utility functions style margin padding top left right bottom horizontal vertical expo ios android mobile web

marginally-pudding's Introduction

Marginally Pudding

About

Create margins and paddings in React Native in the way well known from CSS

How to Install

First, install the library in your project by npm:

$ npm install marginally-pudding

Or Yarn:

$ yarn add marginally-pudding

Getting Started

Connect the library with the project using ES6 import:

import { marginally, pudding } from 'marginally-pudding'

Options

You can use the functions with the following combinations:

(all)
(vertical, horizontal)
(top, horizontal, bottom)
(top, right, bottom, left)

All params are number or string type

Example

import React from 'react'
import { View } from 'react-native'
import { marginally, pudding } from 'marginally-pudding'

const App = () => {
  return (
    <View
      style={{
        backgroundColor: 'red',
        ...marginally(20, 10),
        // marginVertical: 20,
        // marginHorizontal: 10,

        ...pudding(0, 20, 15),
        // paddingTop: 0,
        // paddingHorizontal: 20,
        // paddingBottom: 15,
      }}
    />
  )
}

export default App

License

marginally-pudding's People

Contributors

Stargazers

Watchers

marginally-pudding's Issues

Omit empty (null/undefined) values

Also test object, array etc.

Update gitignore, npmignore file

Remove unused eslint plugins/packages

Remove brackets from switch case

Update eslint + prettier config (ignore files)

auto remove unused imports
require type for type imports
restrict import orders

Update test cases names (variables)

Check if props are valid padding/margin values

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 could benefit from your bug fixes and new features.

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 resolve 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 is some links that can help you:

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.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀