This is an automated email from the ASF dual-hosted git repository.
chaokunyang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fory.git
The following commit(s) were added to refs/heads/main by this push:
new 8bfe1fa8a chore: fix typos (#2429)
8bfe1fa8a is described below
commit 8bfe1fa8a67912712113dd2b3b5411dd889d9b87
Author: co63oc <[email protected]>
AuthorDate: Wed Jul 23 10:04:50 2025 +0800
chore: fix typos (#2429)
<!--
**Thanks for contributing to Fory.**
**If this is your first time opening a PR on fory, you can refer to
[CONTRIBUTING.md](https://github.com/apache/fory/blob/main/CONTRIBUTING.md).**
Contribution Checklist
- The **Apache Fory (incubating)** community has restrictions on the
naming of pr titles. You can also find instructions in
[CONTRIBUTING.md](https://github.com/apache/fory/blob/main/CONTRIBUTING.md).
- Fory has a strong focus on performance. If the PR you submit will have
an impact on performance, please benchmark it first and provide the
benchmark result here.
-->
## What does this PR do?
fix typos
<!-- Describe the purpose of this PR. -->
## Related issues
<!--
Is there any related issue? Please attach here.
- #xxxx0
- #xxxx1
- #xxxx2
-->
## Does this PR introduce any user-facing change?
<!--
If any user-facing interface changes, please [open an
issue](https://github.com/apache/fory/issues/new/choose) describing the
need to do so and update the document if necessary.
-->
- [ ] Does this PR introduce any public API change?
- [ ] Does this PR introduce any binary protocol compatibility change?
## Benchmark
<!--
When the PR has an impact on performance (if you don't know whether the
PR will have an impact on performance, you can submit the PR first, and
if it will have impact on performance, the code reviewer will explain
it), be sure to attach a benchmark data here.
-->
---
dart/packages/fory/lib/src/codegen/analyze/analyzer.dart | 2 +-
.../codegen/analyze/impl/field/{field_sortor.dart => field_sorter.dart} | 0
docs/cpp_debug.md | 2 +-
docs/guide/graalvm_guide.md | 2 +-
4 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/dart/packages/fory/lib/src/codegen/analyze/analyzer.dart
b/dart/packages/fory/lib/src/codegen/analyze/analyzer.dart
index 95541e2dd..46add8502 100644
--- a/dart/packages/fory/lib/src/codegen/analyze/analyzer.dart
+++ b/dart/packages/fory/lib/src/codegen/analyze/analyzer.dart
@@ -23,7 +23,7 @@ import
'package:fory/src/codegen/analyze/impl/annotation/key_annotation_analyzer
import
'package:fory/src/codegen/analyze/impl/constructor/constructor_analyzer.dart';
import 'package:fory/src/codegen/analyze/impl/field/access_info_analyzer.dart';
import 'package:fory/src/codegen/analyze/impl/field/field_analyzer_impl.dart';
-import 'package:fory/src/codegen/analyze/impl/field/field_sortor.dart';
+import 'package:fory/src/codegen/analyze/impl/field/field_sorter.dart';
import 'package:fory/src/codegen/analyze/impl/field/fields_analyzer.dart';
import 'package:fory/src/codegen/analyze/impl/imports/imports_analyzer.dart';
import 'package:fory/src/codegen/analyze/impl/struct/class_analyzer_impl.dart';
diff --git
a/dart/packages/fory/lib/src/codegen/analyze/impl/field/field_sortor.dart
b/dart/packages/fory/lib/src/codegen/analyze/impl/field/field_sorter.dart
similarity index 100%
rename from
dart/packages/fory/lib/src/codegen/analyze/impl/field/field_sortor.dart
rename to
dart/packages/fory/lib/src/codegen/analyze/impl/field/field_sorter.dart
diff --git a/docs/cpp_debug.md b/docs/cpp_debug.md
index f288d28b8..c84935e9a 100644
--- a/docs/cpp_debug.md
+++ b/docs/cpp_debug.md
@@ -23,7 +23,7 @@ license: |
Debug C++ is tricky and binary protocol bug is hard to locate without
debugging support, but setup
debugging support for bazel project is not easy.
-Fory include an out-of-box `launch.json/tasks.json` config in `.vocode`
directory for c++ debugging.
+Fory include an out-of-box `launch.json/tasks.json` config in `.vscode`
directory for c++ debugging.
Just open the fory root directory in vscode, then open a test file such as
`src/fory/row/row_test.cc`,
enter `F5`, then you can debug the c++ code line by line, watch variables, add
breakpoints in vscode just like
diff --git a/docs/guide/graalvm_guide.md b/docs/guide/graalvm_guide.md
index faae421d1..e9bef16a8 100644
--- a/docs/guide/graalvm_guide.md
+++ b/docs/guide/graalvm_guide.md
@@ -30,7 +30,7 @@ any extra cost, the performance is great.
In order to use Fory on graalvm native image, you must create Fory as an
**static** field of a class, and **register** all classes at
the enclosing class initialize time. Then configure `native-image.properties`
under
-`resources/META-INF/native-image/$xxx/native-image.propertie` to tell graalvm
to init the class at native image
+`resources/META-INF/native-image/$xxx/native-image.properties` to tell graalvm
to init the class at native image
build time. For example, here we configure `org.apache.fory.graalvm.Example`
class be init at build time:
```properties
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
