Rename "keep until" conditions to "keep while" conditions

doc/overview.edoc

@@ -171,9 +171,9 @@ tree nodes `stock' and `wood' were created if they were missing. After
 `<<"walnut">>' is removed, they will stay in the tree with possibly neither
 payload nor child nodes.
 
-Khepri has the concept of <em>`keep_until' conditions</em>. A `keep_until'
+Khepri has the concept of <em>`keep_while' conditions</em>. A `keep_while'
 condition is like the conditions which can be used inside path pattern. When a
-node is inserted or updated, it is possible to set `keep_until' conditions:
+node is inserted or updated, it is possible to set `keep_while' conditions:
 when these conditions evaluate to false, the tree node is removed from the
 tree.
 
@@ -182,10 +182,10 @@ to make sure it is removed after its last child node is removed:
 ```
 %% We keep [stock, wood] as long as its child nodes count is strictly greater
 %% then zero.
-KeepUntilCondition = #{[stock, wood] => #if_child_list_length{count = {gt, 0}}}.
+KeepWhileCondition = #{[stock, wood] => #if_child_list_length{count = {gt, 0}}}.
 '''
 
-`keep_until' conditions on self (like the example above) are not evaluated on
+`keep_while' conditions on self (like the example above) are not evaluated on
 the first insert though.
 
 == Khepri API ==

src/internal.hrl

@@ -23,8 +23,8 @@
 
 -record(put, {path :: khepri_path:pattern(),
               payload = none :: khepri_machine:payload(),
-              extra = #{} :: #{keep_until =>
-                               khepri_machine:keep_untils_map()}}).
+              extra = #{} :: #{keep_while =>
+                               khepri_machine:keep_while_conds_map()}}).
 
 -record(delete, {path :: khepri_path:pattern()}).
 

src/khepri.erl

@@ -1009,14 +1009,14 @@ info(StoreId) ->
     Nodes = lists:sort([Node || {_, Node} <- members(StoreId)]),
     lists:foreach(fun(Node) -> io:format("~ts~n", [Node]) end, Nodes),
 
-    case khepri_machine:get_keep_untils_state(StoreId) of
-        {ok, KeepUntils} when KeepUntils =/= #{} ->
+    case khepri_machine:get_keep_while_conds_state(StoreId) of
+        {ok, KeepWhileConds} when KeepWhileConds =/= #{} ->
             io:format("~n\033[1;32m== LIFETIME DEPS ==\033[0m~n", []),
-            WatcherList = lists:sort(maps:keys(KeepUntils)),
+            WatcherList = lists:sort(maps:keys(KeepWhileConds)),
             lists:foreach(
               fun(Watcher) ->
                       io:format("~n\033[1m~p depends on:\033[0m~n", [Watcher]),
-                      WatchedsMap = maps:get(Watcher, KeepUntils),
+                      WatchedsMap = maps:get(Watcher, KeepWhileConds),
                       Watcheds = lists:sort(maps:keys(WatchedsMap)),
                       lists:foreach(
                         fun(Watched) ->

src/khepri_condition.erl

@@ -7,7 +7,7 @@
 
 %% @doc Condition support.
 %%
-%% Conditions can be used in path patterns and `keep_until' conditions.
+%% Conditions can be used in path patterns and `keep_while' conditions.
 %%
 %% A condition is an Erlang record defining a specific property. Some of them
 %% have arguments to further define the condition.
@@ -222,7 +222,7 @@
                                          if_child_list_version() |
                                          if_child_list_length().
 
--type keep_until() :: #{khepri_path:path() => condition()}.
+-type keep_while() :: #{khepri_path:path() => condition()}.
 
 -export([compile/1,
          applies_to_grandchildren/1,
@@ -236,7 +236,7 @@
 
 -export_type([condition/0,
               comparison_op/1,
-              keep_until/0]).
+              keep_while/0]).
 
 -spec compile(Condition) -> Condition when
       Condition :: khepri_path:pattern_component().