Skip to content

Commit 39b5e2c

Browse files
Remove redundant segment separators (#986)
## Goal Remove redundant segment separators from TypeQL core concepts
1 parent aec0f56 commit 39b5e2c

File tree

3 files changed

+0
-11
lines changed

3 files changed

+0
-11
lines changed

core-concepts/modules/ROOT/pages/typeql/entities-relations-attributes.adoc

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,6 @@ E.g., a `person` exists, regardless of whether they are involved in friendships
1616
define
1717
entity person;
1818
entity company;
19-
#!---
2019
----
2120

2221
== Relation
@@ -34,7 +33,6 @@ define
3433
relation employment,
3534
relates employer,
3635
relates employee;
37-
#!---
3836
----
3937

4038
Role type names exist scoped within their relation types, allowing you to re-use role labels in different relation types:
@@ -51,7 +49,6 @@ relation insurance-obligation,
5149
relates employer,
5250
relates employee,
5351
relates insurance;
54-
#!---
5552
----
5653

5754
You can refer to a role distinctly by scoping the role name with the relation name: `employment:employer`.
@@ -74,7 +71,6 @@ A type can be defined to implement this interface using the `owns` keyword.
7471
#!test[schema]
7572
define
7673
attribute age, value integer;
77-
#!---
7874
----
7975

8076
== Owning attributes & playing roles
@@ -89,7 +85,6 @@ E.g., a `person` may own an attribute `birth-date`, or an `employment` may own a
8985
#!test[schema]
9086
define
9187
person owns age;
92-
#!---
9388
----
9489

9590
Entity & relation types may be defined to "play" a role defined by a relation.
@@ -101,7 +96,6 @@ E.g., the entity type `company` may play the `employer` role of an `employment`
10196
#!test[schema, rollback]
10297
define
10398
company plays employment:employer;
104-
#!---
10599
----
106100

107101
== Inheritance

core-concepts/modules/ROOT/pages/typeql/queries-as-functions.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,6 @@ fun post_count($page: page) -> integer:
6767
match
6868
$posting isa posting, links (posted: $page);
6969
return count($posting);
70-
#!---
7170
----
7271

7372
[NOTE]
@@ -98,7 +97,6 @@ match
9897
$_ isa edge, links (from_: $mid, to: $to);
9998
};
10099
return { $to };
101-
#!---
102100
----
103101

104102
This will return `node`s in a breadth-first fashion.

core-concepts/modules/ROOT/pages/typeql/query-variables-patterns.adoc

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,6 @@ match
7474
7575
## $e is an 'employment', where $p plays the 'employee' role
7676
$e isa employment; $e links (employee: $p);
77-
#!---
7877
----
7978

8079
[NOTE]
@@ -88,7 +87,6 @@ match
8887
$p isa person, # Combine the constraints on $p using a comma
8988
has name "James"; # Directly specify type & value of owned attribute.
9089
$e isa employment (employee: $p); # Omit 'links' using the relation shorthand.
91-
#!---
9290
----
9391
We will continue writing out the constraints for illustrative purposes.
9492
====
@@ -138,7 +136,6 @@ insert
138136
139137
## $e is an 'employment', where $p plays the 'employee' role
140138
$e isa employment; $e links (employee: $p);
141-
#!---
142139
----
143140
[NOTE]
144141
====

0 commit comments

Comments
 (0)