735 Commits

Author SHA1 Message Date
d75664e467 docs(changelog): add missing commit 2024-06-05 12:27:06 -04:00
b7489989ed chore(): update package lock files 2024-06-05 16:17:34 +00:00
868ebb7d26 v8.2.1 2024-06-05 16:16:50 +00:00
624ceba2e1 refactor(react): export InputInputEventDetail type (#29512)
Issue number: resolves #29518 

---------

<!-- Please do not submit updates to dependencies unless it fixes an
issue. -->

<!-- Please try to limit your pull request to one type (bugfix, feature,
etc). Submit multiple pull requests if needed. -->

## What is the current behavior?
<!-- Please describe the current behavior that you are modifying. -->
IonInput in React apps can't import the correct type for typescript.  
## What is the new behavior?
<!-- Please describe the behavior or changes that are being added by
this PR. -->
Since it is in the file exported, people using IonInput can import the
correct type.
-
-
-

## Does this introduce a breaking change?

- [ ] Yes
- [x ] No

<!--
  If this introduces a breaking change:
1. Describe the impact and migration path for existing applications
below.
  2. Update the BREAKING.md file with the breaking change.
3. Add "BREAKING CHANGE: [...]" to the commit description when merging.
See
https://github.com/ionic-team/ionic-framework/blob/main/docs/CONTRIBUTING.md#footer
for more information.
-->


## Other information

<!-- Any other information that is important to this PR such as
screenshots of how the component looks before and after the change. -->

Liam DeBeasi told me it was a bug a couple days ago and pointed out to
where it needed to be added.
2024-05-31 22:30:50 +00:00
9bfbd98ea0 chore(): update package lock files 2024-05-22 17:11:57 +00:00
f238b4258c v8.2.0 2024-05-22 17:11:10 +00:00
829a57e7cf docs(changelog): remove already released commits 2024-05-22 12:21:53 -04:00
0f4cca14dc chore(): update package lock files 2024-05-22 16:17:05 +00:00
85728b7b35 v8.1.3 2024-05-22 16:16:15 +00:00
5b07400670 docs(changelog): remove duplicated entries and version comparison 2024-05-15 12:33:52 -04:00
617dfe9c9e chore(): update package lock files 2024-05-15 12:27:50 -04:00
b298c0e015 v8.1.2 2024-05-15 12:27:50 -04:00
217f5bd123 merge release-8.1.1 (#29473) 2024-05-08 14:42:40 -04:00
9a4fa10365 chore(): update package lock files 2024-05-01 14:34:32 +00:00
78d3076703 v8.1.0 2024-05-01 14:33:41 +00:00
665d67778f chore(): update package lock files 2024-05-01 13:59:54 +00:00
101b50e14c v8.0.2 2024-05-01 13:59:14 +00:00
6fd4b50697 chore(): update package lock files 2024-04-24 13:45:53 +00:00
fa60838702 v8.0.1 2024-04-24 13:45:04 +00:00
2d8c9f4942 chore(): update package lock files 2024-04-17 13:52:16 +00:00
bf1ae7b6fe v8.0.0 2024-04-17 13:51:23 +00:00
f7aa4a7e6b chore: clean up changelog 2024-04-17 09:32:04 -04:00
ffd1bf5139 chore(): update package lock files 2024-04-17 13:27:46 +00:00
73af759906 v8.0.0-rc.2 2024-04-17 13:27:08 +00:00
cde84983b2 chore: sync with main 2024-04-17 09:08:24 -04:00
3f3f196a24 chore(): update package lock files 2024-04-17 13:01:00 +00:00
ffce443585 v7.8.5 2024-04-17 12:59:14 +00:00
8259cd0cd9 chore: clean up changelog 2024-04-10 10:18:14 -04:00
638ad30b59 chore(): update package lock files 2024-04-10 14:12:43 +00:00
ea8e220861 v8.0.0-rc.1 2024-04-10 14:11:56 +00:00
d8599b3282 chore: sync with main 2024-04-10 09:50:08 -04:00
1073d22b56 chore(): update package lock files 2024-04-10 13:34:52 +00:00
cea0b493fc v7.8.4 2024-04-10 13:34:07 +00:00
e91fee4f2d Merge remote-tracking branch 'origin/main' into sp/sync-feature-8.0-with-main-04-08 2024-04-08 18:48:00 -04:00
b315b0cb29 chore(docs): consolidate the developer resource files into a docs/ directory (#29266)
Start your review here 👉
[docs/README.md](https://github.com/ionic-team/ionic-framework/blob/FW-6107/docs/README.md)

## What is the current behavior?

Documentation files with information on how to contribute, component
implementations, testing, etc. are scattered throughout various folders
in this repository.

## What is the new behavior?

Consolidates the documentation files into a root `docs/` directory for
easier discovery and organization.

`/docs` tree:

```
├── _config.yml
├── component-guide.md
├── CONTRIBUTING.md
├── README.md
├── sass-guidelines.md
├── angular
│   ├── README.md
│   └── testing.md
├── core
│   ├── README.md
│   └── testing
│       ├── README.md
│       ├── api.md
│       ├── best-practices.md
│       ├── preview-changes.md
│       └── usage-instructions.md
├── react
│   ├── README.md
│   └── testing.md
├── react-router
│   ├── README.md
│   └── testing.md
├── vue
│   ├── README.md
│   └── testing.md
└── vue-router
    ├── README.md
    └── testing.md
```

**Migrates the following:**

| Previous Location | New Location |
| ----------------------------------------------------------- |
----------------------------------------- |
| `.github/COMPONENT-GUIDE.md` | `docs/component-guide.md` |
| `.github/CONTRIBUTING.md` | `docs/CONTRIBUTING.md` |
| `core/scripts/README.md` | `docs/core/testing/preview-changes.md` |
| `core/src/utils/test/playwright/docs/api.md` |
`docs/core/testing/api.md` |
| `core/src/utils/test/playwright/docs/best-practices.md` |
`docs/core/testing/best-practices.md` |
| `core/src/utils/test/playwright/docs/README.md` |
`docs/core/testing/README.md` |
| `core/src/utils/test/playwright/docs/usage-instructions.md` |
`docs/core/testing/usage-instructions.md` |
| `packages/angular/test/README.md` | `docs/angular/testing.md` |
| `packages/react-router/test/README.md` |
`docs/react-router/testing.md` |
| `packages/react/test/README.md` | `docs/react/testing.md` |
| `packages/react/test/base/README.md` | `docs/react/testing.md` |
| `packages/vue/test/README.md` | `docs/vue/testing.md` |

**Adds the following:**

| File | Description |
| ----------------------------- |
-----------------------------------------------------------------------
|
| `docs/sass-guidelines.md` | Sass Variable guidelines taken from
`ionic-framework-design-documents` |
| `docs/README.md` | Entry file that should link to all other files |
| `docs/_config.yml` | Config file for use with GitHub pages |
| `docs/core/README.md` | Description of core, links to contributing and
testing |
| `docs/angular/README.md` | Description of angular, links to
contributing and testing |
| `docs/react/README.md` | Description of react, links to contributing
and testing |
| `docs/react-router/README.md` | Description of react-router, links to
contributing and testing |
| `docs/vue/README.md` | Description of vue, links to contributing and
testing |
| `docs/vue-router/README.md` | Description of vue-router, links to
contributing and testing |
| `docs/vue-router/testing.md` | Testing file for vue-router, populated
from vue-router's main README |

**Does not** add any files for `angular-server`. This is because the
README is essentially empty and there is no testing in that directory. I
can add blank files if we want to have something to add to later.

**Does not** migrate the content of the packages' root `README.md`
files. These files are used for their npm package descriptions so we
should not edit them.

## Hosting Documentation

We can (and should) host these files using GitHub Pages. I have
duplicated them in a personal repository to see how this would look:
[docs-consolidation](https://brandyscarney.github.io/docs-consolidation/).

Doing so will require some formatting fixes (see [Sass
Guidelines](https://brandyscarney.github.io/docs-consolidation/sass-guidelines.html#-reusable-values))
so I did not publish them now but we can easily enable GitHub pages by
toggling a setting in this repository.

## Other information

- Verify that no documentation files were missed in the migration
- You can use these commands to search for `*.md` files in a directory:
    - `find core/src -type f -name "*.md" -print`
- `find packages/angular -type f -name "*.md" -not -path
"**/node_modules/*" -print`
- I did add some redirect links in some of the existing markdown files
so they might still exist for that reason
- We should probably break up the contributing + component guide
documentation into smaller files, such as including best practices, but
I wanted to get everything in the same place first
- The contributing has sections on each of the packages that we could
move to that package's docs folder:
https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#core

---------

Co-authored-by: Maria Hutt <thetaPC@users.noreply.github.com>
2024-04-08 19:06:26 +00:00
ac7631a324 chore: sync with main 2024-04-03 13:17:55 -04:00
101ad5402f chore(): update package lock files 2024-04-03 15:38:52 +00:00
de35fa8b94 v7.8.3 2024-04-03 15:38:11 +00:00
fa387cb2a2 chore(): update package lock files 2024-03-27 15:24:33 +00:00
8ab116150c v8.0.0-rc.0 2024-03-27 15:23:52 +00:00
c0a8e7a95d chore: clean up changelog 2024-03-27 11:02:19 -04:00
0c5a2967d8 chore(): update package lock files 2024-03-27 14:57:27 +00:00
6ebb3c4e38 v8.0.0-beta.4 2024-03-27 14:56:50 +00:00
652ea169b7 chore: update package-lock 2024-03-27 10:29:57 -04:00
42c09a7ea1 chore: sync with main 2024-03-27 09:54:28 -04:00
a2923aaeb3 chore(): update package lock files 2024-03-27 13:34:23 +00:00
eeab96de55 v7.8.2 2024-03-27 13:33:47 +00:00
6c500fd6b2 feat(input): add input-password-toggle component (#29175)
Issue number: Internal

---------

<!-- Please do not submit updates to dependencies unless it fixes an
issue. -->

<!-- Please try to limit your pull request to one type (bugfix, feature,
etc). Submit multiple pull requests if needed. -->

## What is the current behavior?
<!-- Please describe the current behavior that you are modifying. -->

When given a password input it is hard to know what users are typing as
the contents of the input are obscured. As a result, it is a common
pattern to have a button that lets users temporarily toggle the
visibility of the password so they can correct any mistakes. Ionic
currently has the infrastructure for developers to implement this on
their own, but this use case is so common that the team thinks it is
worth having this functionality built-in to Ionic.

## What is the new behavior?
<!-- Please describe the behavior or changes that are being added by
this PR. -->

- Introduces the `ion-input-password-toggle` component. This component
is a button that toggles the visibility of the text in the input it is
slotted into.

## Does this introduce a breaking change?

- [ ] Yes
- [x] No

<!--
  If this introduces a breaking change:
1. Describe the impact and migration path for existing applications
below.
  2. Update the BREAKING.md file with the breaking change.
3. Add "BREAKING CHANGE: [...]" to the commit description when merging.
See
https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer
for more information.
-->


## Other information

<!-- Any other information that is important to this PR such as
screenshots of how the component looks before and after the change. -->


⚠️ Give co-author credit to
https://github.com/ionic-team/ionic-framework/pull/29141 on merge.

Docs PR: https://github.com/ionic-team/ionic-docs/pull/3541

Note: We did not do the approach listed in the other PR due to
https://github.com/ionic-team/ionic-framework/pull/29141#discussion_r1523631811.

---------

Co-authored-by: OS-giulianasilva <OS-giulianasilva@users.noreply.github.com>
2024-03-25 13:22:06 -04:00
90fcddea3d chore: clean up changelog 2024-03-20 10:43:06 -04:00
f6c3141a82 chore(): update package lock files 2024-03-20 14:36:55 +00:00