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: updated description of unsegmented procedures #142

Merged
merged 1 commit into from
Feb 15, 2023
Merged

docs: updated description of unsegmented procedures #142

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
4 changes: 2 additions & 2 deletions documentation/04_basic_features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,8 +55,8 @@ Procedure functions **need to be async** in order to be able to split applicatio

Segment files are used for bundling procedures into servable packages. A procedure must be registered in a segment file in order to be remotely accessible. Procedures can also be registered in multiple segments for optimization reasons (e.g. avoid unnecessary network traffic).

{:.alert-warning}
Unsegmented procedures should only be used locally to avoid import issues.
{:.alert-info}
Unsegmented procedures are available in every segment. To make a procedure only available for a single segment, add the procedure to that segment and set its access to ``private``.

For this example we can create two segment files. The first segment file will only contain the ``sayHello`` procedure.

Expand Down