pgadmin4/web/regression/javascript/schema_ui_files/synonym.ui.spec.js
Ashesh Vashi e9af0c3226
Improved the extendability of the SchemaView and DataGridView. (#7876)
Restructured these modules for ease of maintenance and apply the single
responsibility principle (wherever applicable).

* SchemaView

 - Split the code based on the functionality and responsibility.
 - Introduced a new View 'InlineView' instead of using the
   'nextInline' configuration of the fields to have a better, and
   manageable view.
 - Using the separate class 'SchemaState' for managing the data and
   states of the SchemaView (separated from the 'useSchemaState'
   custom hook).
 - Introduced three new custom hooks 'useFieldValue',
   'useFieldOptions', 'useFieldError' for the individual control to
   use for each Schema Field.
 - Don't pass value as the parameter props, and let the
   'useFieldValue' and other custom hooks to decide, whether to
   rerender the control itself or the whole dialog/view. (single
   responsibility principle)
 - Introduced a new data store with a subscription facility.
 - Moving the field metadata (option) evaluation to a separate place
   for better management, and each option can be defined for a
   particular kind of field (for example - collection, row, cell,
   general, etc).
 - Allow to provide custom control for all kind of Schema field.

* DataGridView

 - Same as SchemaView, split the DataGridView call into smaller,
   manageable chunks. (For example - grid, row, mappedCell, etc).
 - Use context based approach for providing the row and table data
   instead of passing them as parameters to every component
   separately.
 - Have a facility to extend this feature separately in future.
   (for example - selectable cell, column grouping, etc.)
 - Separated the features like deletable, editable, reorder,
   expandable etc. cells using the above feature support.
 - Added ability to provide the CustomHeader, and CustomRow through the
   Schema field, which will extend the ability to customize better.
 - Removed the 'DataGridViewWithHeaderForm' as it has been achieved
   through providing 'CustomHeader', and also introduced
   'DataGridFormHeader' (a custom header) to achieve the same feature
   as 'DataGridViewWithHeaderForm'.
2024-09-09 14:27:31 +05:30

69 lines
1.8 KiB
JavaScript

/////////////////////////////////////////////////////////////
//
// pgAdmin 4 - PostgreSQL Tools
//
// Copyright (C) 2013 - 2024, The pgAdmin Development Team
// This software is released under the PostgreSQL Licence
//
//////////////////////////////////////////////////////////////
import SynonymSchema from '../../../pgadmin/browser/server_groups/servers/databases/schemas/synonyms/static/js/synonym.ui';
import {genericBeforeEach, getCreateView, getEditView, getPropertiesView} from '../genericFunctions';
describe('SynonymSchema', () => {
let schemaObj;
let getInitData = ()=>Promise.resolve({});
beforeEach(() => {
schemaObj = new SynonymSchema(
{
role: ()=>[],
schema: ()=>[],
synobjschema: ()=>[],
getTargetObjectOptions: ()=>[],
},
[],
{
owner: 'postgres',
schema: 'public',
synobjschema: 'public',
}
);
genericBeforeEach();
});
it('create', async () => {
await getCreateView(schemaObj);
});
it('edit', async () => {
await getEditView(schemaObj, getInitData);
});
it('properties', async () => {
await getPropertiesView(schemaObj, getInitData);
});
it('validate', () => {
let state = {};
let setError = jest.fn();
state.name = null;
schemaObj.validate(state, setError);
expect(setError).toHaveBeenCalledWith('name', '\'Name\' cannot be empty.');
state.name = 'my_syn';
state.synobjschema = null;
schemaObj.validate(state, setError);
expect(setError).toHaveBeenCalledWith('synobjschema', '\'Target schema\' cannot be empty.');
state.synobjschema = 'public';
state.synobjname = null;
schemaObj.validate(state, setError);
expect(setError).toHaveBeenCalledWith('synobjname', '\'Target object\' cannot be empty.');
});
});