Describe the bug
There is a horizontal slider in the wrappid-app homepage .

Expected behavior
The page should not have a horizontal slider by default.

Solution

• Remove the default LayoutsAppDiv height and width.

Description

Add functionality in attribution generation script to add fixed header.

Reference

#24

PX tag and IMPORTANT tag required

Describe the bug
On creating Pull Request, es-lint is trying to lint deleted files and failing.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Stack Trace
The stack trace of the bug if any.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Keys having nonmatching space so space should be removed.

Description

Changes in default text color to text secondary dark which has hash color #6D6C6C

What problem we're solving?

need to change the default color of Typograph to TEXT_SECONDARY_DARK

What is the proposed solution?

Made changes in DefaultSCStyles

Additional notes

Description

Using eslint need to implement linting.

Remove unnecessary configs from package.json

Description
Style's npm packages need to be updated to be compatible with updated native-web, native-mobile and core.

Describe the bug
add IMPORTANT to

• h25
• h50
• h75
• h100
• w25
• w50
• w75
• w100

Describe the bug
Old issue reoccurring. On creating Pull Request, es-lint is trying to lint deleted files and failing.
Ref: #47

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Stack Trace
The stack trace of the bug if any.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Description

Add create-tag ci, release ci and publish cd which uses reusable workflows.

References

wrappid/workflows#1

Describe the bug
create instances of different styles of largeCoreStyles, mediumCoreStyles, smallCoreStyles, xLargeCoreStyles, xxLargeCoreStyles in stylesProvider.tsx file.

Describe the bug

Fontsize of corelink is 0.812rem which should be the default size in DefaultSCStyles.ts

Typo in file name in styles/package/base/contants.ts

The name should be constant.ts instead of contants.ts

Desktop

• OS: [Windows 11]
• Browser [Edge]

• Create a LICENSE file from GitHub WebView in main branch
• Choose a license template > MIT License
• Click on Review and submit
• Click on Commit changes
• Change commit message in the dialog Propose changes window

docs: 🔒 license added
  
added MIT License as requested

Ref #[issue-number]

• Change new branch name as WRPD-docs-[issue-number] in the dialog Propose changes window
• Open a pull request to development branch

1. Add respective stylings related to NativeListItemAvatar and NativeListSubheader in DefaultSCStyles and StyledComponentsClasses.

Description

Add script to generate attribution file

Description

Add below keys in package.json and package/package.json

• author
• homepage
• license

Is your feature request related to a problem? Please describe.
1.create wrappid styles for transform Roate, rotateX, rotateY, rotate(-x), rotate(-y), a dotted background and line-height and font-weight.

2. Changes in the bg dotted background and a text styles.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Description:

Need Hover css property to remove styled(MUI) non wrappid componenet.

Originally posted by @irkfaisal in wrappid/guide-module#5 (comment)

Issue

Currently, our application supports only one theme at a time. This limitation restricts users from customizing their experience fully, as they can only choose one theme to apply.

Proposed Solution

To enhance user experience and flexibility, we propose implementing support for multiple themes simultaneously within the application. This would allow users to select and apply multiple themes concurrently, enabling them to mix and match various visual styles according to their preferences.

Expected Behavior

• Users should be able to select and apply multiple themes from the available options.
• The application should seamlessly blend different themes together, ensuring consistency and coherence across the interface.
• Theme preferences should be persistently saved and applied across sessions.

Tasks

1. Design: Discuss and finalize the approach for supporting multiple themes simultaneously.
2. Implementation: Modify the application codebase to accommodate multiple themes concurrently.
3. Testing: Conduct comprehensive testing to ensure that the application functions correctly with multiple themes applied.
4. Documentation: Update the user documentation to include instructions on how to utilize multiple themes.
5. Feedback and Iteration: Gather user feedback and iterate on the implementation as necessary to address any issues or suggestions.

Additional Information

Current application version: 0.0.69
Target platform: [ Mobile | Web ]

1. defaultTheme key removal from WrappidDataContext value.
2. impact handle in styles and wrappid/core#130

Describe the bug
In ConfigProvider if custom config not found returned null.

Additional context
Can't reproduce but code related issues identified and fix required

Any style related changes required while creating styleUtility samples

Additional context
wrappid/guide-module#6

Describe the bug
The font family should not be Roboto
the background utility should have its contrastText maked as important

Possible Solution
The font family should be changed to Rubik
Important tag should be added.

Add a class to give background gradient color

As of now, we provide support for linear gradients only.

Description
change caret(^) to tilde(~) in package.json, and update package-lock.json

Issue Description:

When switching themes in our application, the styles file’s theme properties do not update as expected. This behavior is inconsistent with the intended behavior of theme changes.

Steps to Reproduce:

1. Open the application.
2. Change the theme (e.g., from light mode to dark mode).
3. Observe that the styles defined in the styles file (such as colors, fonts, etc.) do not reflect the updated theme.

Expected Behavior:

When the theme changes, the styles file should dynamically update its theme-related properties to match the selected theme.
Actual Behavior:

The styles file retains the properties from the initial theme, even after switching to a different theme.

Desktop :

• OS: [WINDOWS 11]
• Browser [e.g. chrome, edge]
• Version []

Additional context

• This issue affects user experience and consistency across themes.
• Investigate whether the theme change event is properly triggering updates in the styles file.
• Consider reviewing the theme-related logic in the application code.
• This issue is critical for maintaining a seamless user experience, especially when users switch between light and dark themes. Let’s address this bug promptly!

Describe the bug
After typescript movement, styles package in browser developer tools, not showing. (node_modules/@wrappid/)

To Reproduce
Steps to reproduce the behavior:

1. Open browser (firefox/chrome)
2. Open developer tools
3. Open sources
4. navigate to node_modules/@wrappid

Expected behavior
Show styles package under node_modules/@wrappid in browser dev tools sources

• Create main(default) and development branch.
• GitHub Settings > Branch Rules
  • Nobody able to push directly to above branches except dev-ops activities.
  • Developers needs to create issue branch and commit in that particular branch.
• GitHub Workflow - PR Guardrails
  • Branch Name Validation
  • Conventional Commit
  • Code Linting
• Husky
  • Branch Name Validation
  • Conventional Commit
  • Code Linting
• .eslintrc.js linting config file needs to be present
• must have code:lint and code:format script present in package.json

Don't think a examples directory is needed in this project and can be removed.

Reference

https://github.com/wrappid/styles/security/dependabot/10