Fix #296 fix add & delete entity #297
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughThe recent updates enhance the application's graph and schema management features, introducing conditional behaviors based on user input and improving component interactions. Key modifications include refined state management, streamlined functionality for creating and deleting graphs and schemas, and enhanced visual aesthetics. These changes collectively aim to bolster user experience and maintainability within the graph visualization and manipulation interface. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Header
participant GraphView
participant API
User->>Header: Create Graph/Schema
Header->>GraphView: Set dynamic name
GraphView->>API: Send create request
API-->>GraphView: Return success message
GraphView-->>User: Show success notification
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Outside diff range, codebase verification and nitpick comments (1)
app/create/page.tsx (1)
21-21: The commented-out state management forschemainapp/create/page.tsxaffects other parts of the codebase.The search results indicate multiple references to
schemaacross various files, includingapp/schema/SchemaView.tsxandapp/create/page.tsx. This suggests that theschemastate is still being used in the codebase, and commenting it out may lead to functionality issues.
app/schema/SchemaView.tsx: Multiple references toschema.app/create/page.tsx: Several commented-out lines related toschema.Please review and address these references to ensure the functionality is not disrupted.
Analysis chain
LGTM! But verify the impact on the codebase.
The state management for
schemahas been commented out. Ensure that this does not affect other parts of the code.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that the commented-out schema state management does not affect other parts of the code. # Test: Search for the usage of `schema` in the codebase. Expect: No occurrences. rg --type tsx 'schema'Length of output: 50
Script:
#!/bin/bash # Description: Verify that the commented-out schema state management does not affect other parts of the code. # Test: Search for the usage of `schema` in the codebase. Expect: No occurrences. rg 'schema'Length of output: 8146
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (20)
- app/api/graph/[graph]/route.ts (1 hunks)
- app/api/graph/model.ts (11 hunks)
- app/components/Header.tsx (3 hunks)
- app/components/graph/DeleteGraph.tsx (1 hunks)
- app/components/ui/Avatar.tsx (2 hunks)
- app/components/ui/combobox.tsx (4 hunks)
- app/create/page.tsx (5 hunks)
- app/globals.css (1 hunks)
- app/graph/GraphDataPanel.tsx (4 hunks)
- app/graph/GraphView.tsx (16 hunks)
- app/graph/Selector.tsx (5 hunks)
- app/graph/labels.tsx (1 hunks)
- app/graph/page.tsx (4 hunks)
- app/graph/toolbar.tsx (3 hunks)
- app/schema/SchemaCreateElement.tsx (1 hunks)
- app/schema/SchemaDataPanel.tsx (1 hunks)
- app/schema/SchemaView.tsx (9 hunks)
- app/schema/page.tsx (3 hunks)
- lib/utils.ts (2 hunks)
- tailwind.config.js (1 hunks)
Files skipped from review due to trivial changes (1)
- tailwind.config.js
Additional comments not posted (95)
lib/utils.ts (2)
3-3: LGTM! Enhances type safety and clarity.The new type
ElementDataDefinitionimproves type definitions related to graph elements.Also applies to: 7-7
41-41: LGTM! Improves function flexibility.The optional parameter
qallows the function to be called without providing an argument, defaulting to a predefined Cypher query string.app/components/ui/Avatar.tsx (1)
13-13: LGTM! Enhances performance and prevents stale state updates.The
useEffecthook ensures thatsetUserStatusis only invoked when thesessionorsetUserStatuschanges.Also applies to: 18-20
app/globals.css (1)
47-47: LGTM! Improves responsiveness and visual structure.The new utility class enhances the layout and appearance of the
.DataPanelcomponent.app/graph/labels.tsx (2)
30-30: LGTM! Conditional className application enhances styling flexibility.The use of the
cnutility function to conditionally apply the class based oncategory.nameis a good practice.
33-33: LGTM! Increased icon size improves visibility and interaction.The change from
w-4 h-4tow-6 h-6enhances the icon's visibility and user interaction.app/components/graph/DeleteGraph.tsx (5)
4-9: LGTM! The newisSchemaparameter enhances functionality.The addition of the
isSchemaparameter allows the component to handle both graph and schema deletions effectively.
12-12: LGTM! Thetypeconstant improves readability.Using a constant to determine the type of entity being deleted enhances code readability and maintainability.
15-15: LGTM! Constructing thenameconstant ensures correct endpoint usage.Appending
_schematographNamewhenisSchemais true ensures that the correct endpoint is used for deletion.
21-21: LGTM! Dynamic toast notification message enhances user experience.Displaying either "Graph" or "Schema" based on the
typeconstant provides clear feedback to the user.
22-22: LGTM! PassinggraphNameto theonDeleteGraphcallback enhances flexibility.The modification allows the caller to receive the specific name of the deleted entity, improving the callback's usability.
app/schema/page.tsx (6)
4-4: LGTM! Necessary utility imports for the new functionality.The imports from "@/lib/utils" are required for data fetching, preparing arguments, and displaying toast notifications.
14-15: LGTM! State variables for tracking edge and node counts.The introduction of
edgesCountandnodesCountstate variables is necessary for managing and displaying graph-related data.
Line range hint
20-47:
LGTM! UpdateduseEffecthook for fetching node and edge counts.The additional fetch calls for node and edge counts ensure that the component has accurate and up-to-date data. The logic is well-structured and handles potential errors gracefully.
30-30: LGTM! Constructing thenameconstant ensures correct endpoint usage.Appending
_schematoschemaNameensures that the correct endpoint is used for fetching node and edge counts.
36-39: LGTM! Fetch call for node counts.The fetch call retrieves the count of nodes and updates the
nodesCountstate variable. The logic is correctly implemented and handles potential errors gracefully.
40-43: LGTM! Fetch call for edge counts.The fetch call retrieves the count of edges and updates the
edgesCountstate variable. The logic is correctly implemented and handles potential errors gracefully.app/graph/page.tsx (5)
12-13: State variables added correctly.The state variables
edgesCountandnodesCountare initialized correctly.
40-44: FirstuseEffecthook handles graph state correctly.The hook resets the graph state when the graph name changes.
46-48: SeconduseEffecthook fetches counts correctly.The hook fetches the counts whenever the graph name or the
fetchCountfunction changes.
19-38: FunctionfetchCountadded correctly.The function correctly fetches the counts of nodes and edges and updates the state variables. Ensure the fetch calls are correctly handled.
However, verify the URLs used in the fetch calls to ensure they are correct.
Verification successful
URLs in
securedFetchcalls are correctly used.The URLs used in the
securedFetchcalls within thefetchCountfunction are correctly formatted and consistent with the expected API endpoints.
app/graph/page.tsx: Verified the URLs used insecuredFetchcalls.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the URLs used in the fetch calls. # Test: Search for the usage of `securedFetch`. Expect: Correct URLs. rg --type js -A 5 $'securedFetch'Length of output: 32
Script:
#!/bin/bash # Description: Verify the URLs used in the fetch calls. # Test: Search for the usage of `securedFetch` in all files and include more context. rg -A 10 'securedFetch'Length of output: 35704
58-64: Functionrunmodified correctly.The function correctly calls
fetchCountafter retrieving query results.However, verify the URLs used in the fetch calls to ensure they are correct.
Verification successful
URLs used in fetch calls are correct.
The
securedFetchfunction is used with appropriate URLs across the codebase, primarily targeting API endpoints under/api/graph/.
- Example URLs:
api/user/api/graph/${prepareArg(graphName)}/?query=${q[0]}api/uploadScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the URLs used in the fetch calls. # Test: Search for the usage of `securedFetch`. Expect: Correct URLs. rg --type js -A 5 $'securedFetch'Length of output: 32
Script:
#!/bin/bash # Description: Verify the URLs used in the fetch calls within app/graph/page.tsx. # Test: Search for all fetch calls within the specified file. rg 'fetch\(' -A 5 app/graph/page.tsxLength of output: 38
Script:
#!/bin/bash # Description: Verify the URLs used in the fetch calls across the entire codebase. # Test: Search for all fetch calls across the entire codebase. rg 'fetch\(' -A 5Length of output: 275
Script:
#!/bin/bash # Description: Verify the context of fetch calls by searching for the definition and usage of `input` in lib/utils.ts. # Test: Search for the definition and usage of `input` in lib/utils.ts. rg 'input' -A 5 lib/utils.tsLength of output: 576
Script:
#!/bin/bash # Description: Verify the URLs used in the fetch calls by searching for calls to the `securedFetch` function across the codebase. # Test: Search for calls to the `securedFetch` function across the codebase. rg 'securedFetch\(' -A 5Length of output: 14470
app/graph/toolbar.tsx (2)
20-21: State variabledeleteOpenadded correctly.The state variable
deleteOpenis initialized correctly.
37-41: FunctionhandleDeleteElementadded correctly.The function handles the deletion of elements and updates the state correctly.
app/api/graph/[graph]/route.ts (1)
134-140: Parametercreatehandled correctly inGETfunction.The
createparameter is correctly handled, and the control flow is updated accordingly.app/components/ui/combobox.tsx (5)
25-27: New properties added toComboboxPropsinterface.The additions of
isSchema,defaultOpen, andonOpenChangeprovide enhanced flexibility and control over the Combobox component.
30-30: UpdatedComboboxfunction parameters.The new properties
isSchema,defaultOpen, andonOpenChangeare correctly included with default values.
32-36: State initialization updated.The
useStatehook for theopenstate now utilizes thedefaultOpenprop, allowing for greater flexibility in managing the dropdown's visibility.
59-65: NewhandelDeletefunction added.The
handelDeletefunction effectively manages the deletion of options and updates the state accordingly.
93-96: UpdatedDropdownMenu'sonOpenChangeevent and component rendering.The
onOpenChangeprop is correctly utilized, and the visibility ofUploadGraphandDeleteGraphcomponents is properly managed based on the state.Also applies to: 196-214
app/components/Header.tsx (4)
30-30: Newtypevariable introduced.The
typevariable correctly determines whether the context is for a "Graph" or "Schema" based on the pathname.
35-46: UpdatedhandelCreateGraphfunction.The
handelCreateGraphfunction correctly uses the newnamevariable and updates the success message to reflect the type of entity being created.
69-76: Updated button labels and dialog titles.The dynamic inclusion of the type in button labels and dialog titles improves clarity in the user interface.
Also applies to: 87-91
Line range hint
91-106:
Updated form for creating a new graph/schema.The form correctly uses the new
graphNamestate and handles the creation process effectively.app/api/graph/model.ts (8)
25-30: ReorderedCOLORS_ORDER_VALUEarray.The reordering of the
COLORS_ORDER_VALUEarray is noted. Ensure that this change does not negatively impact the application.
56-61: SimplifiedgetCategoryColorValueandgetCategoryColorNamefunctions.The functions correctly return the indexed color value and name, respectively.
63-66: NewgetCategoryColorNameFromValuefunction added.The function correctly retrieves the category name based on the color value.
123-150: New getter and setter methods added.The new getter and setter methods provide encapsulated access to
Categories,Labels,CategoriesMap,LabelsMap,NodesMap, andEdgesMap.
Line range hint
181-220:
UpdatedextendNodemethod.The method correctly handles the node creation and updates the state accordingly. The removal of the
newElementsparameter simplifies the interface.
Line range hint
224-275:
UpdatedextendEdgemethod.The method correctly handles the edge creation and updates the state accordingly. The removal of the
newElementsparameter simplifies the interface.
Line range hint
281-315:
Updatedextendmethod.The method correctly handles the extension process and updates the state accordingly. The removal of the
newElementsarray from its parameters simplifies the interface.
316-328: NewupdateCategoriesmethod added.The method correctly handles the category updates based on conditions and updates the state accordingly.
app/create/page.tsx (6)
10-13: LGTM! Unused imports commented out.The imports for
GraphandSchemaViewhave been commented out, indicating they are no longer used.
197-197: LGTM! But verify the impact on the rendering.The rendering logic for
SchemaViewhas been commented out. Ensure that this does not affect the rendering of the component.
60-60: LGTM! But verify the impact on the functionality.The
setSchemafunction call within theuseEffecthook has been commented out. Ensure that this does not affect the functionality of theuseEffecthook.
Line range hint
229-229:
LGTM! But verify the impact on the codebase.The
GraphViewfunction call has been commented out. Ensure that this does not affect other parts of the code.Verification successful
The commented-out
GraphViewfunction call inapp/create/page.tsxdoes not affect other parts of the codebase.
- The
GraphViewcomponent is still used inapp/graph/page.tsxand defined inapp/graph/GraphView.tsx.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that the commented-out GraphView function call does not affect other parts of the code. # Test: Search for the usage of `GraphView` in the codebase. Expect: No occurrences. rg --type tsx 'GraphView'Length of output: 53
Script:
#!/bin/bash # Description: Verify that the commented-out GraphView function call does not affect other parts of the code. # Test: Search for the usage of `GraphView` in the codebase. Expect: No occurrences. rg 'GraphView'Length of output: 436
Line range hint
106-106:
LGTM! But verify the impact on the codebase.The
setLabelfunction has been commented out. Ensure that this does not affect other parts of the code.Verification successful
Commenting out the
setLabelfunction inapp/create/page.tsxdoes not impact other parts of the codebase.The
setLabelfunction is a state setter created byuseStatehooks in various files, and each instance is scoped to its respective component.
- No further action is required.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that the commented-out setLabel function does not affect other parts of the code. # Test: Search for the usage of `setLabel` in the codebase. Expect: No occurrences. rg --type tsx 'setLabel'Length of output: 52
Script:
#!/bin/bash # Description: Verify that the commented-out setLabel function does not affect other parts of the code. # Test: Search for the usage of `setLabel` in the codebase. Expect: No occurrences. rg 'setLabel'Length of output: 1571
Script:
#!/bin/bash # Description: Verify the definition of setLabel to determine if the commented-out function in app/create/page.tsx is the same as the ones used in other files. # Test: Search for the definition of setLabel in the codebase. rg 'function setLabel' --context 5Length of output: 36
Script:
#!/bin/bash # Description: Verify if setLabel is defined as a state setter function using useState. # Test: Search for useState hooks that define setLabel in the codebase. rg 'useState.*setLabel'Length of output: 25
Script:
#!/bin/bash # Description: Verify if setLabel is defined as a state setter function using useState. # Test: Search for all useState occurrences and include context to identify setLabel definitions. rg 'useState' --context 5Length of output: 38105
Line range hint
250-250:
LGTM! But verify the impact on the codebase.The
setPropertyfunction has been commented out. Ensure that this does not affect other parts of the code.Verification successful
The commented-out
setPropertyfunction does not affect other parts of the codebase.The
setPropertyfunction inapp/graph/GraphView.tsxandapp/graph/GraphDataPanel.tsxare independent implementations and are not related to the commented-out function inapp/create/page.tsx.
app/graph/GraphView.tsx: Defines and uses its ownsetPropertyfunction.app/graph/GraphDataPanel.tsx: Uses asetPropertyfunction passed as a prop.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that the commented-out setProperty function does not affect other parts of the code. # Test: Search for the usage of `setProperty` in the codebase. Expect: No occurrences. rg --type tsx 'setProperty'Length of output: 55
Script:
#!/bin/bash # Description: Verify that the commented-out setProperty function does not affect other parts of the code. # Test: Search for the usage of `setProperty` in the codebase. Expect: No occurrences. rg 'setProperty'Length of output: 1183
Script:
#!/bin/bash # Description: Verify the definitions and usages of `setProperty` in the identified files. # Find the definition and usage of `setProperty` in `app/graph/GraphView.tsx` rg --context 5 'setProperty' app/graph/GraphView.tsx # Find the definition and usage of `setProperty` in `app/graph/GraphDataPanel.tsx` rg --context 5 'setProperty' app/graph/GraphDataPanel.tsxLength of output: 5176
app/graph/Selector.tsx (6)
3-3: LGTM! Import statements updated.The import statements have been updated to include
DispatchandSetStateActionto support the new props for state management.
17-26: LGTM! Function signature updated.The function signature of
Selectorhas been expanded to include additional props:edgesCount,nodesCount,setEdgesCount, andsetNodesCount.
28-31: LGTM! State management updated.The state management for
options,schema,selectedValue,duplicateOpen,dropOpen,queriesOpen, andqueryhas been added to enhance the state management capabilities of the component.
45-45: LGTM!useEffectupdated.The
useEffecthook has been updated to fetch graph names and update options based onrunQuery.
66-75: LGTM!handleOnChangefunction updated.The
handleOnChangefunction has been updated to fetch and set the schema ifrunQueryis true.
258-260: LGTM!SchemaViewintegration updated.The
SchemaViewcomponent has been updated to include the newly introducedsetEdgesCountandsetNodesCountprops, enhancing the interactivity of the schema display.app/schema/SchemaCreateElement.tsx (6)
1-13: LGTM! Import statements added.The import statements include various UI components and utility functions necessary for the functionality of the
SchemaCreateElementcomponent.
15-21: LGTM!Propsinterface added.The
Propsinterface defines the expected props for theSchemaCreateElementcomponent.
27-35: LGTM! State management added.The state management includes various states necessary for managing the attributes, labels, and other interactive elements of the component.
37-55: LGTM!handelAddAttributefunction added.The
handelAddAttributefunction handles the addition of new attributes, ensuring they are correctly added to the state.
57-81: LGTM!handelSetAttributefunction added.The
handelSetAttributefunction handles the setting of attribute values, ensuring they are correctly updated in the state.
83-94: LGTM!handelOnCreatefunction added.The
handelOnCreatefunction handles the creation of new elements, ensuring they are correctly created based on the provided attributes and label.app/graph/GraphDataPanel.tsx (2)
13-13: Narrowed type definition forobjproperty.The
objproperty in thePropsinterface now only acceptsElementDataDefinition. Ensure that this change does not break existing functionality that relied on the previous broader type definition.
31-31: Renamed exported function for clarity.The exported function name has been changed from
DataPaneltoGraphDataPanel, which enhances clarity regarding the component's purpose and context within the application.app/graph/GraphView.tsx (6)
4-4: Updated imports for type definitions.The imports have been updated to include
ElementDataDefinitionfromcytoscape, aligning with the updated type definitions in the component.
140-145: Added props for dynamic node and edge count management.The component's props have been updated to include
setNodesCountandsetEdgesCount, enhancing its functionality by allowing dynamic management of node and edge counts.
149-150: Updated state management for multiple selections.The state management has been updated to accommodate an array of selected elements instead of a single selected element, enhancing the selection logic and improving user interaction.
318-334: Enhanced selection logic for multiple selections.The selection logic has been enhanced to support the new
handleBoxSelectedmethod, enabling users to select multiple nodes or edges at once, improving usability.
400-443: Overhauled deletion functionality for multiple elements.The
onDeleteElementmethod has been replaced withhandelDeleteElement, which processes the deletion of multiple selected elements, improving functionality and user experience.
572-574: UpdatedDataPanelcomponent usage.The
DataPanelcomponent usage has been updated to reflect the newobjproperty type and the newhandelDeleteElementmethod, aligning with the updated type definitions and deletion functionality.app/schema/SchemaDataPanel.tsx (5)
3-10: Approved imports for new component.The imports include various UI components and utility functions necessary for the functionality of the new component.
27-34: ApprovedPropsinterface.The
Propsinterface is well-defined and covers all necessary properties for the component's functionality.
36-36: ApprovedemptyAttributefunction.The
emptyAttributefunction returns an empty attribute array, useful for initializing the state of a new attribute.
38-418: ApprovedSchemaCreateElementcomponent.The
SchemaCreateElementcomponent is well-structured and provides comprehensive functionality for managing schema data, including adding, editing, and deleting attributes, as well as setting the label.
40-54: Approved use of state and effect hooks.The use of state and effect hooks is appropriate and ensures the component's state is managed correctly.
app/schema/SchemaView.tsx (22)
44-47: LGTM!The updated styles for selection boxes, nodes, and edges improve visual clarity.
Also applies to: 56-56, 82-85
100-101: LGTM!The
getElementIdfunction is a useful utility for retrieving element IDs and query types.
102-107: LGTM!The
getCreateQueryfunction constructs appropriate query strings for creating nodes or edges.
110-117: LGTM!The new state variables effectively manage the selection state, panel state, and addition state of entities and relations.
118-134: LGTM!The new
useEffecthooks ensure the component state is correctly updated in response to changes in the schema and user actions.
138-148: LGTM!The
onCategoryClickfunction correctly toggles the visibility of nodes based on their category and relayouts the elements.
155-165: LGTM!The
onLabelClickfunction correctly toggles the visibility of edges based on their label and relayouts the elements.
170-176: LGTM!The
handelSetSelectedElementfunction correctly manages the selected element state and the data panel state.
178-180: LGTM!The
handleTapfunction correctly updates the selected nodes state based on the tapped node.
183-202: LGTM!The
handleSelectedfunction correctly updates the styles of selected elements and sets the selected element state.
204-220: LGTM!The
handleBoxSelectedfunction correctly updates the styles of box-selected elements and sets the selected elements state.
222-235: LGTM!The
handleUnselectedfunction correctly resets the styles of unselected elements and clears the selected elements state.
237-244: LGTM!The
handleMouseOverfunction correctly updates the styles of edges on mouse over.
246-254: LGTM!The
handleMouseOutfunction correctly resets the styles of edges on mouse out.
Line range hint
255-265:
LGTM!The
onExpandfunction correctly toggles the expanded state of the data panel.
266-312: LGTM!The
handelDeleteElementfunction correctly deletes the selected elements from the graph and updates the state.
314-333: LGTM!The
handelSetAttributefunction correctly sets the attribute for the selected element and updates the schema.
335-395: LGTM!The
handelSetLabelfunction correctly sets the label for the selected element and updates the schema.
397-418: LGTM!The
handelRemovePropertyfunction correctly removes the property from the selected element and updates the schema.
421-447: LGTM!The
onCreateElementfunction correctly creates a new element (node or edge) in the graph and updates the state.
Line range hint
449-549:
LGTM!The return statement correctly integrates the updated
SchemaDataPanelandCreateElementcomponents and handles their state.
20-22: Verify the usage of the updated Props interface.The Props interface now requires
setNodesCountandsetEdgesCount. Ensure all instances ofSchemaVieware updated to pass these required props.Verification successful
Verified the usage of the updated Props interface.
The Props interface now requires
setNodesCountandsetEdgesCount, and all instances ofSchemaViewin the codebase have been updated to pass these required props.
app/schema/page.tsxapp/graph/Selector.tsxScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify all instances of SchemaView usage in the codebase to ensure they pass the required props. # Test: Search for the SchemaView component usage. Expect: Only occurrences with the new required props. rg --type tsx -A 5 $'SchemaView'Length of output: 59
Script:
#!/bin/bash # Description: Verify all instances of SchemaView usage in the codebase to ensure they pass the required props. # Test: Search for the SchemaView component usage. Expect: Only occurrences with the new required props. rg --glob '*.tsx' -A 5 $'SchemaView'Length of output: 2888
Summary by CodeRabbit
New Features
Enhancements
DeleteGraph,Selector, andToolbarcomponents through better handling of graph and schema actions.SchemaCreateElementandSchemaDataPanelto allow for more dynamic interaction with schema attributes.Bug Fixes
Style Changes
Documentation