*Replace this paragraph with a description of what this PR is changing
or adding, and why. Consider including before/after screenshots.*
*List which issues are fixed by this PR. For larger changes, raising an
issue first helps
reduce redundant work.*
## Pre-launch Checklist
- [ ] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [ ] I signed the [CLA].
- [ ] I read the [Contributors Guide].
- [ ] I updated/added relevant documentation (doc comments with `///`).
- [ ] All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-devrel
channel on [Discord].
<!-- Links -->
[Flutter Style Guide]:
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
[CLA]: https://cla.developers.google.com/
[Discord]: https://github.com/flutter/flutter/wiki/Chat
[Contributors Guide]:
https://github.com/flutter/samples/blob/main/CONTRIBUTING.md
Bumps [jni](https://github.com/dart-lang/jnigen) from 0.6.1 to 0.7.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/dart-lang/jnigen/releases">jni's releases</a>.</em></p>
<blockquote>
<h2>package:jni v0.7.0</h2>
<ul>
<li><strong>Breaking Change</strong> (<a href="https://redirect.github.com/dart-lang/jnigen/issues/387">#387</a>): Added <code>JBuffer</code> and <code>JByteBuffer</code> classes as default classes for <code>java.nio.Buffer</code> and <code>java.nio.ByteBuffer</code> respectively.</li>
<li><strong>Breaking Change</strong>: Made the type classes <code>final</code>.</li>
<li>Fixed a bug where <code>addAll</code>, <code>removeAll</code> and <code>retainAll</code> in <code>JSet</code> would run their respective operation twice.</li>
<li>Fixed a bug where <code>JList.insertAll</code> would not throw the potentially thrown Java exception.</li>
</ul>
<h2>package:jnigen v0.7.0</h2>
<ul>
<li><strong>Breaking Change</strong> (<a href="https://redirect.github.com/dart-lang/jnigen/issues/387">#387</a>): Added <code>JBuffer</code> and <code>JByteBuffer</code> classes as default classes for <code>java.nio.Buffer</code> and <code>java.nio.ByteBuffer</code> respectively.</li>
<li><strong>Breaking Change</strong>: Made the type classes <code>final</code>.</li>
<li>Added <code>ignore_for_file: lines_longer_than_80_chars</code> to the generated file preamble.</li>
<li>Added an explicit cast in generated <code><Interface>.implement</code> code to allow <code>dart analyze</code> to pass when <code>strict-casts</code> is set.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a href="https://github.com/dart-lang/jnigen/commits/jni-v0.7.0">compare view</a></li>
</ul>
</details>
<br />
[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=jni&package-manager=pub&previous-version=0.6.1&new-version=0.7.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
This change removes an unused parameter that was recently removed in the
`RenderEditable` on the `master` branch
https://github.com/flutter/flutter/pull/109114.
Fixes#1923
## Pre-launch Checklist
- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] All existing and new tests are passing.
---------
Co-authored-by: Brett Morgan <brett.morgan@gmail.com>
- Fixes#1899 - Don't use BuildContext in async.
- Disabled build script for `next-gen-ui-demo` for master channel
because dependency gap does not compile.
- Improve use BuildContext in `place_tracker`, added checks to verify
that the context is still mounted, and avoid passing BuildContext as
parameter.
## Pre-launch Checklist
- [ ] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [ ] I signed the [CLA].
- [ ] I read the [Contributors Guide].
- [ ] I updated/added relevant documentation (doc comments with `///`).
- [ ] All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-devrel
channel on [Discord].
<!-- Links -->
[Flutter Style Guide]:
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
[CLA]: https://cla.developers.google.com/
[Discord]: https://github.com/flutter/flutter/wiki/Chat
[Contributors Guide]:
https://github.com/flutter/samples/blob/main/CONTRIBUTING.md
## Pre-launch Checklist
- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I updated/added relevant documentation (doc comments with `///`).
- [ ] All existing and new tests are passing.
---------
Co-authored-by: David Iglesias <ditman@gmail.com>
Co-authored-by: Mark Thompson <2554588+MarkTechson@users.noreply.github.com>
Co-authored-by: John Ryan <ryjohn@google.com>
* Added sample code for using plugins and channels from background isolates.
* goderbauer feedback 1
* goderbauer feedback2
* goderbauer feedback 3
* Add `background_isolate_channels` to CI
* Comment in `background_isolate_channels`
* Fixup
* Elide `experimental/material_3_demo` from `master`
* Elide `material_3_demo` from `master` CI
* Elide `place_tracker` on `master` CI
---------
Co-authored-by: Brett Morgan <brettmorgan@google.com>
Co-authored-by: Brett Morgan <brett.morgan@gmail.com>
* added Type Jam puzzle app for review
* pr round 2 prep
* updated ci scripts for varfont_shader_puzzle
* resolved unused and minor variable naming issues
* rotator tiles row and col are final vars now
* removed unused import and print from production
* made constructors const where needed
* pages_flow export refactored to directly come from that file
* removed old api commented out section from FragmentShaded
* updated pubspec yaml to correct project name
* dart min version updated; removed unnecessary commented out dependencies from pubspec.yaml
* updated pubspec.yaml min flutter version to ensure FragmentShader support
* added/edited comments for explanation, esp on var fonts; removed obsolete comments
* trailing newline added to pubspec.yaml eof
* flutter create
* Copied in from 'contextual-menu-examples' repo
* Works again with the latest updates to the branch
* Clean up anywhere example
* Clean up other examples
* Add to CI
* Updated with release version of context menus, and added platform switcher
* Generated files
* Home icon on your original platform
* Remove web_dashboard from ci, not sure why that change was there...
* Add context_menu to beta channel, but commented out, for the future
* +x permissions on the master script, which I may have accidentally changed before?
* Actual bash comment
* dart format
* Natural default platform'
* A working test, for the email page
* Import order fix
* Test some pages
* More tests
* dart format
* Revert "Revert "Add code sharing sample (#1444)" (#1464)"
This reverts commit dc50c46ef1.
* Opting out failing tests on Windows for CI
Co-authored-by: Craig Labenz <craig.labenz@gmail.com>
* code-sharing boilerplate
* initial commit of code-sharing logic
* documentation improvements
* added code-sharing to samples.yaml
* Updated counter UI to visually indicate communication with the server
* added code_sharing to CI
* CI changes to code_sharing
* fixed test with DI
* formatting
* added shared module to CI
* adds forgotten CI change
* Added components
* Added test
* Added README
* Run flutter format
* Added all the updated components and tests
* Added README file
* Update README.md
* Add textfields to M3 demo app
* move textfield to exprerimental/
* Update component_screen_test.dart
* Fixed comment: changed sdk version
* Changed all double quotes to single
* Added trailing comma, changed all private fields to public except private state classes
* Added enum for screen selection
* Removed comment for material_3_demo
* Added experimental m3 demo app to master CI pipeline
* fixed failing tests
* Modified the analysis_options.yaml
* Fixed warning
* Ran flutter format command
Co-authored-by: Qun Cheng <quncheng@google.com>
Co-authored-by: hangyu <108393416+hangyujin@users.noreply.github.com>