From 12749fa107268880c4ad6fd26a9e02dd87d0080a Mon Sep 17 00:00:00 2001 From: keikeicheung Date: Tue, 28 Nov 2023 16:03:05 +0800 Subject: [PATCH] #992 fix typos --- docs/providers_tables_viewports/lifecycle.md | 2 +- docs/providers_tables_viewports/modules.md | 2 +- docs/roadmap.mdx | 3 +++ docs/rpc/service.md | 2 +- docs/team.mdx | 6 ++++-- docs/trees/trees_session_tables.md | 2 +- docs/ui/calculated_columns.md | 2 +- docs/ui/visual_linking.md | 2 +- .../packages/vuu-datagrid/src/grid-model/gridModelUtils.ts | 2 +- .../finos/vuu/provider/join/JoinManagerEventDataSink.scala | 2 +- 10 files changed, 15 insertions(+), 10 deletions(-) diff --git a/docs/providers_tables_viewports/lifecycle.md b/docs/providers_tables_viewports/lifecycle.md index a051edaf1..f1bc03de3 100644 --- a/docs/providers_tables_viewports/lifecycle.md +++ b/docs/providers_tables_viewports/lifecycle.md @@ -9,7 +9,7 @@ which allows components to be started and stopped in a sensible order. ## How does the lifecycle work? -The user interaction with the lifecycle component is very minimal by design. THe obligation is when there is a component +The user interaction with the lifecycle component is very minimal by design. The obligation is when there is a component that depends on something else, it registers that dependency in the construction logic. As an example if we take the VuiStateStoreProvider diff --git a/docs/providers_tables_viewports/modules.md b/docs/providers_tables_viewports/modules.md index 63d7be524..7b82a385c 100644 --- a/docs/providers_tables_viewports/modules.md +++ b/docs/providers_tables_viewports/modules.md @@ -85,7 +85,7 @@ class VuiStateStoreProvider(val table: DataTable, val store: VuiStateStore)(impl } ``` -In the module we also define a rest service. This is how the UI interacts with the state store. THe rest service is exposed via the underlying Vert.x +In the module we also define a rest service. This is how the UI interacts with the state store. The rest service is exposed via the underlying Vert.x infrastructure. ```scala diff --git a/docs/roadmap.mdx b/docs/roadmap.mdx index 23176e4ab..c73671707 100644 --- a/docs/roadmap.mdx +++ b/docs/roadmap.mdx @@ -4,3 +4,6 @@ title: Vuu Roadmap --- This is the Vuu Roadmap: +1. Big Data Support +2. Data Visualization +3. User Experience diff --git a/docs/rpc/service.md b/docs/rpc/service.md index 8cb4e0abd..22d4adfed 100644 --- a/docs/rpc/service.md +++ b/docs/rpc/service.md @@ -5,7 +5,7 @@ import { SvgDottySeparator } from "@site/src/components/SvgDottySeparator"; The best way to describe service rpc calls is with an example. In the default React grid for Vuu, we have the filter -component. The filter uses an ALNTR grammar for defining how we want to filter the data. Examples of how we use this are: +component. The filter uses an ANTLR grammar for defining how we want to filter the data. Examples of how we use this are: ``` ric = AAA.L diff --git a/docs/team.mdx b/docs/team.mdx index e2c49ff7d..5cbe99c08 100644 --- a/docs/team.mdx +++ b/docs/team.mdx @@ -12,8 +12,10 @@ This is the Vuu team (this is not an exhaustive list of contributors): - Michael Banham, UBS, Contributor - Marina Bambang, UBS, Product Owner - Justyna Klos, So In Your Face LTD, Designer -- Colin Eberhardt, Scottlogic, Contributor +- Colin Eberhardt, Scott Logic, Contributor - Dimitar Dimitrov, UBS, Contributor - Gareth Ncube, UBS, Contributor - Pranav Bheemsetty, UBS, Contributor -- Harry Hartley, Scottlogic, Contributor +- Harry Hartley, Scott Logic, Contributor +- Na-Lee Ha, UBS, Contributor +- Tomasz Rumak, UBS, Contributor diff --git a/docs/trees/trees_session_tables.md b/docs/trees/trees_session_tables.md index 5cd26a208..7dfabf748 100644 --- a/docs/trees/trees_session_tables.md +++ b/docs/trees/trees_session_tables.md @@ -7,5 +7,5 @@ import { SvgDottySeparator } from "@site/src/components/SvgDottySeparator"; In this section you can read about: - [Trees](trees.md) - the datastructures used, how the system looks -- [Aggregates](aggregates.md) - these are mathematical operations we want to do across the leaves of a tree, which are displayed at teh branch level +- [Aggregates](aggregates.md) - these are mathematical operations we want to do across the leaves of a tree, which are displayed at the branch level - [Tree Builder](tree_builder.md) - the server side component that builds the trees diff --git a/docs/ui/calculated_columns.md b/docs/ui/calculated_columns.md index 497aa12d8..679724fb3 100644 --- a/docs/ui/calculated_columns.md +++ b/docs/ui/calculated_columns.md @@ -51,7 +51,7 @@ It would likely be poor UX to ask the user to define the return type. ### Use in Tree'd Viewports -By default calculated columns would work the same in tree'd viewports as in non-tree'd viewports. THe only caveat to that +By default calculated columns would work the same in tree'd viewports as in non-tree'd viewports. The only caveat to that would be when the calculated column would be a branch in the tree. In that case the column values would have to be calculated in the tree building function, which may slow down tree generation for specific viewports. diff --git a/docs/ui/visual_linking.md b/docs/ui/visual_linking.md index 1b66269b9..9515efee9 100644 --- a/docs/ui/visual_linking.md +++ b/docs/ui/visual_linking.md @@ -34,7 +34,7 @@ Example: ``` If you look at this code from our SimulationModule, you can see we've declared a potential link from this table ChildOrders to parentOrders. -THe structure of the declaration is: Link(fieldInChildTable, parentTable, fieldInParentTable) +The structure of the declaration is: Link(fieldInChildTable, parentTable, fieldInParentTable) Anytime you declare these links, our UI will allow you to select the Visual Linking usimng a right click on the grid. diff --git a/vuu-ui/packages/vuu-datagrid/src/grid-model/gridModelUtils.ts b/vuu-ui/packages/vuu-datagrid/src/grid-model/gridModelUtils.ts index 2c1fe5feb..77118addb 100644 --- a/vuu-ui/packages/vuu-datagrid/src/grid-model/gridModelUtils.ts +++ b/vuu-ui/packages/vuu-datagrid/src/grid-model/gridModelUtils.ts @@ -264,7 +264,7 @@ function updateGroupColumnWidth( * 2) adjust the flex of resized column, distribute diff to the other flex columns * if we are resizing a non-flex column * 1) adjust the width of all other fill columns according to their flex values - * if we try to adjust teh width of a flex column and it is the only flex column + * if we try to adjust the width of a flex column and it is the only flex column * disallow the resize */ function updateGroupFillColumnWidth( diff --git a/vuu/src/main/scala/org/finos/vuu/provider/join/JoinManagerEventDataSink.scala b/vuu/src/main/scala/org/finos/vuu/provider/join/JoinManagerEventDataSink.scala index aa8e95d69..a4a502917 100644 --- a/vuu/src/main/scala/org/finos/vuu/provider/join/JoinManagerEventDataSink.scala +++ b/vuu/src/main/scala/org/finos/vuu/provider/join/JoinManagerEventDataSink.scala @@ -11,7 +11,7 @@ import java.util.concurrent.ConcurrentHashMap case class JoinDefToJoinTable(joinDef: JoinTableDef, table: DataTable) /** - * THe purpose of this object is to allow us to go from a right key, say prices, ric = VOD.L and look + * The purpose of this object is to allow us to go from a right key, say prices, ric = VOD.L and look * For the corresponding left keys, say orders, orderId = 1,2,3 */ class RightToLeftKeys {