Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(agama): change the file name #7680

Merged
merged 1 commit into from
Feb 8, 2024
Merged

docs(agama): change the file name #7680

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
0 .../developer/agama/recommended-practices.md → ...n/developer/agama/agama-best-practices.md
View file
Open in desktop
File renamed without changes.
2 changes: 1 addition & 1 deletion docs/admin/developer/agama/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,4 +180,4 @@ You can assign this value to a variable at the top of your loop declaration. See

### Can Agama code be called from Java?

No. These two languages are supposed to play roles that should not be mixed, check [here](./recommended-practices.md#about-flow-design).
No. These two languages are supposed to play roles that should not be mixed, check [here](./agama-best-practices#about-flow-design).
4 changes: 2 additions & 2 deletions docs/admin/developer/agama/jans-agama-engine.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -260,7 +260,7 @@ As seen in the examples Agama engine can deal with Java exceptions, however, thi

[Agama types](../../../agama/language-reference.md#data-types) do not match Java types. This means passing a "native" Agama value as parameter in a method `Call` requires some form of compatibility with the target (Java) type in the method signature.

An argument (Agama value) is compatible with a method parameter if it can be "converted" successfully. As we'll see, conversion feels pretty natural in practice. If this process fails a `java.lang.IllegalArgumentException` is thrown and the flow will crash unless the exception is caught. Note however the recommended practice is to let flows [crash](./recommended-practices.md#about-crashes).
An argument (Agama value) is compatible with a method parameter if it can be "converted" successfully. As we'll see, conversion feels pretty natural in practice. If this process fails a `java.lang.IllegalArgumentException` is thrown and the flow will crash unless the exception is caught. Note however the recommended practice is to let flows [crash](./agama-best-practices#about-crashes).

The following lists some of the most common successful conversions:

Expand Down Expand Up @@ -353,4 +353,4 @@ We consider the following to be remarkable:

### OOP prose warning

See the recommended [practices](./recommended-practices.md#oop-prose-warning) to learn more about this topic.
See the recommended [practices](./agama-best-practices#oop-prose-warning) to learn more about this topic.
2 changes: 1 addition & 1 deletion mkdocs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -283,7 +283,7 @@ nav:
- Agama engine: admin/developer/agama/jans-agama-engine.md
- Navigation, UI pages and assets: admin/developer/agama/flows-navigation-ui.md
- Projects deployment: admin/developer/agama/projects-deployment.md
- Recommended practices: admin/developer/agama/recommended-practices.md
- Agama Best Practices: admin/developer/agama/agama-best-practices.md
- Advanced usages: admin/developer/agama/advanced-usages.md
- Engine and bridge configurations: admin/developer/agama/engine-bridge-config.md
- FAQ: admin/developer/agama/faq.md
Expand Down