skynexui / components Goto Github PK

vercel/next.js#33326

🚨 The automated release from the main 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 main 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.

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Why

• Document: It's important to people see the available props and be aware that web supports everything while our list is related to props that are common in Flutter and React

How

• Use Flutter test for flutter and the Box component
• Use react testing library for react and the Box component
• Try to sync this docs inside storybook also
• inside "examples" add small examples related to the styled that are being created

DoD

• Have in skynexui.dev in the section "Stylesheet" all props properly documented

Why?
People need to have an easy way to add new features and fix bugs

How?
Create a "build:watch": "" command that allows to work inside the examples folder with a live build and doing yarn link inside the respective folders.

I believe that we could use nodemon and use it's exec command to always run yarn unlink && yarn build && yarn link

Why

• MVP for allow me to release a small app with it

How

• Style: overflowY with list view under the hood;
• Style: borderRadius Left|Right|Top|Bottom supporting string to enable fine tuning in future;
• #53
• #54
• #48
• #59
• #58
• #55
• #49
• #56
• #57
• #60
• #61
• #62
• #63
• #64

Definition of Done

• To have all How topics implemented

Actually isn't possible to render anything because we only have components related to style

How

• React: ...
• Flutter: ...

Definition of Done

• To be able to render a list;
• This list must have scroll;
• We should be able to provide how many columns will have

🚨 The automated release from the main 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 main 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.

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Why

• Image elements must have an alt prop, either with meaningful text, or an empty string for decorative images.

How

• Add a alt prop to <Image /> component

Why?
...

How?
...

Following a boilerplate from Alura Imersão React - Aula 01

I've encountered two TypeScript issues:

• backgroundImage
• backgroundRepeat
• backgroundSize
• backgroundBlendMode
• minHeight

does not exist in type StyleSheet

textFieldColors props: positive, negative are mandatory and should be optional (?)

• Project
• Reference

Why

• ...

How

• ...

DoD

• ...

Why

• Right now we are not able to put more than one children inside Box component, it simply doesn't show anything

How

• We will have a property called flex-direction based in the CSS Prop
• Name: flexDirection
• Values: 'row' | 'column'
• Default: 'row'

Definition of Done

• Be able to have 2 or more child being displayed inside a box component in React and Flutter

Why
Because will make easier ensure that all commits are being done thinking in Semantic Release

How
We could just use Husky and Commitzen like this video:

• https://youtu.be/F3B8W3yPPSo
• https://youtu.be/1eTofdmfq1g

Why
Because right now it's very hard to keep 2 repos, I believe that with only one will be easier to keep everything in sync.

How

• ...

DoD
Have the docs being deployed over this repository

Why?
Just because packages folder should be destinated to additional packages related to the core

How?
Just move the folder to a projects new one at the root

Why
Works with expo and it's a good way to see how we could abstract access through links in future

How
I believe that make a simple working example with stack navigation and a button moving inside and moving forward

Why

• Because right now we are not able to do this.

How

• It must receive a URL and just render an image;

Definition of Done

• To be able to display images

i did the steps from here: https://github.com/skynexui/core#contributing,

but i still getting this error during yarn install in monorepo example (in fact, in any of the examples): error Couldn't find package "@skynexui/native" on the "npm" registry.

it seems to be the same problem here: yarnpkg/yarn#2611

I'm using yarn 1.22.11 in a Linux Mint OS with node v14.17.5 (in case it is related to the build scripts)

🚨 The automated release from the main 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 main 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.

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Why
Because right now, only the JavaScript version is being automatically released to NPM and GitHub Registry

How
We can follow this tutorial, seems very usefull:

• https://birju.dev/posts/publish-your-flutter-package-using-github-actions/
• https://stackoverflow.com/questions/70487479/whats-the-new-location-of-credentials-json-for-dart-flutter-pub

# 1 - get the credentials
cat "$HOME/Library/Application Support/dart/pub-credentials.json"

# 2 - save them as secrets in GH

# 3 - Follow the post:
# https://birju.dev/posts/publish-your-flutter-package-using-github-actions/

DoD
After every new merge on main we will have a new release.

Script build is running export:docs and publishing all *.mdx files into npm package and this is increasing the packet size

"build": "yarn export:types && rollup -c && yarn export:docs"

Why

• The provider component is the entry point of all configurations

How

• Flutter and React

  • Create a context around the entire app called Provider
  • Create a hook to get access to the theme called useTheme()
  • ...

• API

  • Provider named SkynexUIProvider
  • useTheme()

Usage example

• Demo

How the theme will be?

{
  "colors": {
      "...": "..."
  },
  "components": {
    "textField": {
      "variant": "basicBordered"
    }
  }
}

DoD

• To be able to provide a theme as a JSON and the app work as expected

Why

• ...

How

• ...

DoD

• ...

Why

Will be very interesting have support to Storybook to make easier the process of creation and documentation of the components

How?
Follow the storybook instructions

• Reference: https://github.com/omariosouto/mariosouto.com/blob/main/packages/universal-ui/src/theme/foundation/space/space.stories.mdx