Merge pull request #1468 from gluestack/release/@gluestack-ui/themed@…

…1.0.25

release: @gluestack-ui/[email protected]

.changeset/config.json

@@ -7,5 +7,5 @@
   "access": "public",
   "baseBranch": "main",
   "updateInternalDependencies": "patch",
-  "ignore": ["@gluestack/ui-storybook"]
+  "ignore": ["@gluestack/ui-storybook", "@gluestack/ui-storybook"]
 }

.eslintignore

@@ -1,11 +1,12 @@
-
 packages/**/dist
 packages/**/build
 packages/**/node_modules
 packages/**/lib
 packages/**/cli.js
 
 packages/ui/components
+packages/**/example
+
 
 # packages/**/example
 # !.build/test.js

.gitattributes

@@ -0,0 +1,3 @@
+*.pbxproj -text
+# specific for windows script files
+*.bat text eol=crlf

.github/workflows/auto-assign-issue.yml

@@ -0,0 +1,17 @@
+name: Issue assignment
+
+on:
+  issues:
+    types: [opened, edited, labeled]
+
+jobs:
+  auto-assign:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Auto-assign issue'
+        uses: pozil/auto-assign-issue@v1
+        with:
+          repo-token: ${{ secrets.MY_GITHUB_TOKEN }}
+          teams: dank-style-support
+          numOfAssignee: 1
+          allowSelfAssign: false

.github/workflows/auto-assign-pr.yml

@@ -2,7 +2,7 @@ name: PR assignment
 
 on:
   pull_request:
-    types: [opened, reopened]
+    types: [opened, edited, synchronize, reopened]
 
 jobs:
   auto-assign:

.github/workflows/lighthouse.yml_old

@@ -2,7 +2,7 @@ name: Vercel Preview URL Lighthouse Audit
 
 on:
   pull_request:
-    branches: ["master"]
+    branches: ['master']
 
 jobs:
   generate_lighthouse_audit:

.github/workflows/main.yml_old

@@ -4,14 +4,14 @@ name: Run Tests and Check for build
 
 # Controls when the workflow will run
 on:
-  # Triggers the workflow on push or pull request events but only for the "main" branch
+  # Triggers the workflow on push or pull request events but only for the "master" branch
   # push:
-  #   branches: [ "main" ]
+  #   branches: ['master']
   pull_request:
     branches: ['master']
 
   # Allows you to run this workflow manually from the Actions tab
-  workflow_dispatch:
+  # workflow_dispatch:
 
 concurrency: ${{ github.workflow }}-${{ github.ref }}
 

.github/workflows/testing.yml_old

@@ -0,0 +1,22 @@
+# name: 'Unit test'
+# run-name: 'Unit Test'
+# on: [pull_request]
+# jobs:
+#   test:
+#     runs-on: ubuntu-latest
+#     steps:
+#       - name: Checkout repository
+#         uses: actions/checkout@v2
+
+#       - uses: actions/setup-node@v3
+#         with:
+#           node-version: 16.x
+
+#       - name: Print Repo Name
+#         run: echo ${{ github.event.client_payload.message.repo }}
+
+#       - name: Install Dependencies
+#         run: yarn
+
+#       - name: Run Tests
+#         run: yarn test

.gitignore

@@ -37,4 +37,4 @@ yarn-error.log*
 .turbo
 .vercel
 
-packages/gluestack-style
+packages/gluestack-style

.npmignore

@@ -0,0 +1,2 @@
+!build
+src

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing to `gluestack/gluestack-ui`
 
-We'd love for you to contribute to our source code and to make `gluestack/ui` even better than it is
+We'd love for you to contribute to our source code and to make `gluestack-style` even better than it is
 today! Here are some guidelines we'd like you to follow:
 
 - [Contributing to `gluestack/gluestack-ui`](#contributing-to-gluestack-ui)
@@ -26,7 +26,7 @@ If you are eager to start contributing code right away, you can go through [`glu
 There are other ways you can contribute without writing a single line of code. Here are a few things you can do to help out:
 
 1. **Replying and handling open issues.** We get a lot of issues every day, and some of them may lack necessary information. You can help out by guiding people through the process of filling out the issue template, asking for clarifying information, or pointing them to existing issues that match their description of the problem.
-2. **Reviewing pull requests for the docs.** Reviewing [documentation updates](https://github.com/gluestack/ui-docs/pulls) can be as simple as checking for spelling and grammar. If you encounter situations that can be explained better in the docs, click **Edit** at the bottom left of most docs pages to get started with your own contribution.
+2. **Reviewing pull requests for the docs.** Reviewing [documentation updates](https://github.com/gluestack/gluestack-style/pulls) can be as simple as checking for spelling and grammar. If you encounter situations that can be explained better in the docs, click **Edit** at the bottom left of most docs pages to get started with your own contribution.
 3. **Help people write test plans.** Some pull requests sent to the main repository may lack a proper test plan. These help reviewers understand how the change was tested, and can speed up the time it takes for a contribution to be accepted.
 
 Each of these tasks is highly impactful, and maintainers will greatly appreciate your help.
@@ -58,7 +58,7 @@ If you find a bug in the source code, you can help us by submitting an issue to
 
 ### <a name="feature"></a> Missing a Feature?
 
-You can request a new feature by submitting an issue to our [GitHub Repository](https://github.com/gluestack/ui/issues).
+You can request a new feature by submitting an idea to our discussion under [Feature Request](https://github.com/gluestack/gluestack-style/discussions/new?category=feature-request) category.
 
 If you would like to implement a new feature then consider what kind of change it is:
 
@@ -82,9 +82,9 @@ with quickly:
 
 - **Issue Description** - if an error is being thrown a non-minified stack trace helps
 - **Motivation for or Use Case** - explain why this is a bug for you
-- **`gluestack/ui` Version(s)** - is it a regression?
+- **`gluestack-style` Version(s)** - is it a regression?
 - **Browsers and Operating System** - is this a problem with all browsers or only specific ones?
-- **Reproduce the Error** - provide a live example (using [expo snack](https://snack.expo.io/) or an unambiguous set of steps.
+- **Reproduce the Error** - provide a live example (using [expo snack template](https://snack.expo.dev/@gluestack/4da9b2) or an unambiguous set of steps.
 - **Related Issues** - has a similar issue been reported before?
 - **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be
   causing the problem (line of code or commit)
@@ -99,7 +99,7 @@ with quickly:
   git clone [email protected]:${YOUR_USERNAME}/gluestack/gluestack-ui.git
   ```
 
-- Navigate to ui
+- Navigate to gluestack-style
 
   ```
   cd gluestack-ui

LICENSE

@@ -13,6 +13,7 @@ The above copyright notice and this permission notice shall be included in all
 copies or substantial portions of the Software.
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
 FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
 COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER

README.md

@@ -5,6 +5,7 @@
     <img src="https://raw.githubusercontent.com/gluestack/gluestack-ui/main/img/gluestack-ui-banner.svg" alt="gluestack-ui logo" >
   </a>
   <br>
+  <br>
 </h3>
 
 ## Introduction
@@ -17,13 +18,13 @@ You can find detailed documentation for each component, including a list of prop
 
 ## Features
 
-- **Customizable components:** Each component in the library comes with a set of customizable props that allow you to tailor its appearance and behavior to your specific needs.
+- **Dynamic styles:** Using JavaScript expressions, you can create dynamic styles that change based on the state of your components.
 
-- **Responsive design:** The components are built using modern web design principles and are fully responsive, so they work seamlessly across a wide range of devices and screen sizes.
+- **Server-side rendering (SSR) support:** This allows you to use the same styles on the server and the client, making it easy to implement SSR for your React applications..
 
-- **Well-documented:** The comes with comprehensive documentation for each component, including a list of props and examples, to help you get up and running quickly.
+- **Responsive styling::** This allows you to easily create responsive styles that adapt to different screen sizes and resolutions.
 
-- **Easy to use:** The components are designed to be easy to use and integrate into your existing React applications. Simply install the library and import the components you need.
+- **Theme support:** You can easily define and switch between different themes for your application, allowing for a consistent design across all pages.
 
 - **Frequent updates:** We are constantly working on improving the library and adding new components. Follow us on GitHub to stay up-to-date on the latest releases and features.
 
@@ -58,18 +59,29 @@ function App({ children }) {
 }
 ```
 
-2. Now you can start using components!:
+2. Now you can use `@gluestack-style/react` to style your components by using the `styled` function provided by the library. For example:
 
 ```jsx
 import { Button, ButtonText } from '@gluestack-ui/themed';
 
-function Example() {
+const StyledButton = styled(
+  Pressable,
+  {
+    bg: '$red500',
+    p: '$3',
+  },
+  {}
+);
+
+const StyledButtonText = styled(Text, {}, {});
+
+export const App = () => {
   return (
     <Button>
       <ButtonText>Awesome Button!</ButtonText>
     </Button>
   );
-}
+};
 ```
 
 More guides on how to get started are available