183 Commits

Author SHA1 Message Date
6877d659d3 chore(): update package lock files 2023-08-16 14:23:51 +00:00
16f7ec2284 v7.3.0 2023-08-16 14:23:33 +00:00
7c24965216 chore(): update package lock files 2023-08-16 13:26:24 +00:00
ffe5307905 v7.2.4 2023-08-16 13:26:09 +00:00
3a263d14c3 chore(): update package lock files 2023-08-09 16:28:15 +00:00
0cb37430d3 v7.2.3 2023-08-09 16:27:57 +00:00
01857dd315 chore(): update package lock files 2023-08-02 15:59:53 +00:00
dbe6f390ef v7.2.2 2023-08-02 15:59:37 +00:00
960adbbc5c chore(): update package lock files 2023-07-26 15:54:44 +00:00
db29871654 v7.2.1 2023-07-26 15:54:29 +00:00
08cc3d93ae chore(): update package lock files 2023-07-19 16:29:26 +00:00
8661e21674 v7.2.0 2023-07-19 16:29:12 +00:00
ddfbc9faef Merge remote-tracking branch 'origin/main' into final-7.2-sync 2023-07-19 09:52:12 -04:00
f18da214bc chore(): update package lock files 2023-07-19 13:08:31 +00:00
7e174849b5 v7.1.4 2023-07-19 13:08:11 +00:00
90f41243d9 feat(angular): support binding routing data to component inputs (#27694)
Issue number: Resolves #27476

---------

<!-- 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. -->

Ionic Angular application on Angular v16 cannot use the
[`bindToComponentInputs`](https://angular.io/api/router/ExtraOptions#bindToComponentInputs)
feature to assign route parameters, query parameters, route data and
route resolve data to component inputs.

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

- Ionic Angular developers can use the option on `RouterModule.forRoot`
to enable the Angular feature for binding the route snapshot data to the
component inputs.

**Modules**
```ts
@NgModule({
  imports: [
    RouterModule.forRoot([/* your routes */], { 
      bindToComponentInputs: true // <-- enable this feature
    })
  ]
})
export class AppModule { }
```

**Standalone**

```ts
import { withComponentInputBinding } from '@angular/router';

bootstrapApplication(App, {
  providers: [
    provideRouter(routes, 
      //... other features
      withComponentInputBinding() // <-- enable this feature
    )
  ],
});
```

With this feature enabled, developers can bind route parameters, query
parameters, route data and the returned value from a resolver to input
bindings on their component.

For example, with a route configuration of:
```ts
RouterModule.forChild([
  {
    path: ':id',
    data: {
      title: 'Hello world'
    },
    resolve: {
      name: () => 'Resolved name'
    },
    loadComponent: () => import('./example-component/example.component').then(c => c.ExampleComponent)
  }
])
```
and a component configuration of:

```ts
@Component({ }) 
export class ExampleComponent {
  @Input() id?: string;
  @Input() title?: string;
  @Input() name?: string;
  @Input() query?: string;
}
```

Navigating to the component with a url of: `/2?query=searchphrase`

The following would occur:
- `id` would return `2`
- `title` would return `Hello world`
- `name` would return `Resolved name`
- `query` would return `searchphrase`

## Does this introduce a breaking change?

- [ ] Yes
- [x] No

<!-- If this introduces a breaking change, please describe the impact
and migration path for existing applications below. -->


## Other information

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

This PR will need to be targeted to a minor release once a design doc is
approved by the team.

Dev-build: `7.1.3-dev.11689276547.129acb40`
2023-07-18 16:26:37 -04:00
71310372c9 feat(searchbar): add name property (#27737)
resolves #27675
2023-07-17 11:43:00 -04:00
d6c812f785 chore(): update package lock files 2023-07-12 12:54:58 +00:00
0c9392abd6 v7.1.3 2023-07-12 12:54:40 +00:00
61486d97f7 chore(): update package lock files 2023-07-06 16:40:18 +00:00
20331458de v7.1.2 2023-07-06 16:40:00 +00:00
32bc33ed28 refactor(angular): move to packages directory (#27719)
Issue number: N/A

---------

<!-- 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. -->

The `angular` directory sits at the root of the project instead of in
`packages` with all the other JS Framework integrations. This does not
cause any functional issues with Ionic, but it is confusing since
integrations are not in a consistent place.

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

- Moves the `angular` directory to `packages/angular`

Note: Most files should remain unchanged. The only files I changed are
the files that had direct paths to the old `angular` directory:

1. Removes the `angular` path in `lerna.json`. This is now covered by
`packages/*`
2. Updated the angular file path in `.gitignore`
3. Updates the path to the angular package in `stencil.config.ts` for
the Angular Output Targets
4. Updates some of Angular's sync scripts to correctly get the core
stylesheets as well as the core package.
5. Updates the test app sync script to correctly sync core and
angular-server

~I'm not entirely sure why GitHub thinks
https://github.com/ionic-team/ionic-framework/pull/27719/files#diff-f5bba7e7c7c75426e2b9c89868310cb03890493b4efe0252adf8d12cc8398962
is a new file since it exists in `main` here:
1f06be4a31/angular/test/base/scripts/build-ionic.sh~
Fixed in
6e7fc49827

## Does this introduce a breaking change?

- [ ] Yes
- [x] No

<!-- If this introduces a breaking change, please describe the impact
and migration path for existing applications below. -->


## Other information

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

Dev build: `7.1.2-dev.11688052109.13454f5c`
2023-07-05 17:52:35 +00:00
d37623a2ca chore(packages): move the packages to root 2018-03-12 16:02:25 -04:00
851aa838fa refactor(router): init ng router refactor 2018-03-06 19:57:45 -06:00
a1f942d45e chore(cleanup): remove unused code 2018-03-06 19:56:53 -06:00
056ec4b666 @ionic/angular 0.0.2-29 2018-03-05 14:45:02 +01:00
dcbaf5e7ec Angular needs <2.7? 2018-03-05 14:45:01 +01:00
4ec3e488ea fix(zone): forgot to remove console.logs 2018-03-04 16:08:30 +01:00
aa91d11726 fix(testing): do not throw error for missing Ionic global 2018-03-04 07:29:16 -06:00
b4590f4849 chore(build): create npm run build.link 2018-03-04 06:10:15 -06:00
239b0aa1bb chore(build): update build scripts 2018-03-03 16:16:10 -06:00
06abbf069f chore(): update to latest ionic/core 2018-03-03 16:35:41 +01:00
8b605bf2d2 chore(): update to latest stencil 2018-03-03 16:11:52 +01:00
4e0ffbb82c chore(build): add changelog 2018-03-03 00:06:19 -06:00
8d704947b9 chore(build): update build scripts 2018-03-03 00:03:27 -06:00
afd89e77e4 chore(build): update build scripts 2018-03-02 23:57:52 -06:00
62523c32bb chore(deploy): update deploy version script 2018-03-02 23:18:03 -06:00
7366c38abc perf(events): bypass ngzone 2018-03-02 22:56:39 -06:00
b3ff101fa8 chore(deploy): update deploy script 2018-03-02 22:45:21 -06:00
756dc6e306 refactor(events): remove Events feat from core 2018-03-02 14:52:34 -06:00
79eddec369 fix(events): fix ionic/angular events 2018-03-01 16:32:29 -06:00
9c93df48d8 style(lint): fix lint errors 2018-03-01 16:21:06 -06:00
e84ddb69dc fix(events): create events module and remove ion-events component 2018-03-01 16:06:59 -06:00
217c51e4c5 0.0.2-28 2018-03-01 13:23:16 -05:00
a8e42e32cb chore(angular): run build first 2018-03-01 13:20:06 -05:00
b94ba2ae02 0.0.2-27 2018-03-01 13:19:38 -05:00
db9b5ccb90 chore(np): add np 2018-03-01 13:13:05 -05:00
95abd46ada chore(build): update tsconfig build and package 2018-02-28 14:45:21 -06:00
1e6cccf784 docs(readme): update readmes 2018-02-28 14:45:21 -06:00
c3362fecd5 fix(angular): move module sensitive controllers out of forRoot() 2018-02-28 11:46:17 -06:00