pgadmin4/web/regression/javascript/schema_ui_files/functions.ui.spec.js

467 lines
10 KiB
JavaScript
Raw Permalink Normal View History

/////////////////////////////////////////////////////////////
//
// pgAdmin 4 - PostgreSQL Tools
//
2024-01-01 02:43:48 -06:00
// Copyright (C) 2013 - 2024, The pgAdmin Development Team
// This software is released under the PostgreSQL Licence
//
//////////////////////////////////////////////////////////////
import BaseUISchema from 'sources/SchemaView/base_schema.ui';
import FunctionSchema from '../../../pgadmin/browser/server_groups/servers/databases/schemas/functions/static/js/function.ui';
import {genericBeforeEach, getCreateView, getEditView, getPropertiesView} from '../genericFunctions';
class MockSchema extends BaseUISchema {
get baseFields() {
return [];
}
}
describe('FunctionSchema', ()=>{
//Procedure schema
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 03:57:31 -05:00
const procedureSchemaObj = new FunctionSchema(
()=>new MockSchema(),
()=>new MockSchema(),
{
role: [],
schema: [],
getLanguage: [],
getTypes: [],
getSupportFunctions: [],
},
{
node_info: {
connected: true,
user: {id: 10, name: 'postgres', is_superuser: true, can_create_role: true, can_create_db: true},
user_id: 1,
username: 'postgres',
version: 130005,
server: {
host: '127.0.0.1',
port: 5432,
server_type: 'postgres',
user: {
id: 10,
name: 'postgres',
is_superuser: true,
can_create_role: true,
can_create_db: true,
},
} },
},
{
type: 'procedure',
},
{
funcowner: 'postgres',
pronamespace: 'public',
}
);
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 03:57:31 -05:00
const createSchemaObj = () => new FunctionSchema(
() => new MockSchema(),
() => new MockSchema(),
{
role: [],
schema: [],
getLanguage: [],
getTypes: [],
getSupportFunctions: [],
},
{
node_info: {
connected: true,
user: {
id: 10,
name: 'postgres',
is_superuser: true,
can_create_role: true,
can_create_db: true,
},
user_id: 1,
username: 'postgres',
version: 130005,
server: {
host: '127.0.0.1',
port: 5432,
server_type: 'postgres',
user: {
id: 10,
name: 'postgres',
is_superuser: true,
can_create_role: true,
can_create_db: true,
},
},
},
},
{
type: 'function',
},
{
funcowner: 'postgres',
pronamespace: 'public',
}
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 03:57:31 -05:00
);
let schemaObj = createSchemaObj();
let getInitData = ()=>Promise.resolve({});
beforeEach(()=>{
genericBeforeEach();
});
it('create', async ()=>{
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 03:57:31 -05:00
await getCreateView(createSchemaObj());
});
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 03:57:31 -05:00
it('create procedure', async ()=>{
await getCreateView(procedureSchemaObj);
});
it('edit', async ()=>{
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 03:57:31 -05:00
await getEditView(createSchemaObj(), getInitData);
});
it('properties', async ()=>{
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 03:57:31 -05:00
await getPropertiesView(createSchemaObj(), getInitData);
});
it('proiswindow visible', async ()=>{
let editSchemaObj = new FunctionSchema(
() => new MockSchema(),
() => new MockSchema(),
{
role: [],
schema: [],
getLanguage: [],
getTypes: [],
getSupportFunctions: [],
},
{
node_info: {
catalog: {},
connected: true,
user_id: 1,
username: 'postgres',
version: 130005,
server: {
host: '127.0.0.1',
port: 5432,
server_type: 'postgres',
user: {
id: 10,
name: 'postgres',
is_superuser: true,
can_create_role: true,
can_create_db: true,
},
},
},
},
{
type: 'function',
},
{
funcowner: 'postgres',
pronamespace: 'public',
}
);
let initData = ()=>Promise.resolve({
sysfunc: true,
type: 'function',
});
await getEditView(editSchemaObj, initData);
});
it('proiswindow visible', async ()=>{
let editSchemaObj = new FunctionSchema(
() => new MockSchema(),
() => new MockSchema(),
{
role: [],
schema: [],
getLanguage: [],
getTypes: [],
getSupportFunctions: [],
},
{
node_info: {
catalog: {},
connected: true,
user_id: 1,
username: 'postgres',
version: 130005,
server: {
host: '127.0.0.1',
port: 5432,
server_type: 'postgres',
user: {
id: 10,
name: 'postgres',
is_superuser: true,
can_create_role: true,
can_create_db: true,
},
},
},
},
{
type: 'function',
},
{
funcowner: 'postgres',
pronamespace: 'public',
}
);
let initData = ()=>Promise.resolve({
sysproc: true,
type: 'function',
});
await getEditView(editSchemaObj, initData);
});
let initDataProc = ()=>Promise.resolve({
sysfunc: true,
type: 'procedure',
});
it('proiswindow visible', async ()=>{
let editSchemaObj = new FunctionSchema(
() => new MockSchema(),
() => new MockSchema(),
{
role: [],
schema: [],
getLanguage: [],
getTypes: [],
getSupportFunctions: [],
},
{
node_info: {
connected: true,
user_id: 1,
username: 'postgres',
version: 130005,
server: {
host: '127.0.0.1',
port: 5432,
server_type: 'postgres',
user: {
id: 10,
name: 'postgres',
is_superuser: true,
can_create_role: true,
can_create_db: true,
},
},
},
},
{
type: 'procedure',
},
{
funcowner: 'postgres',
pronamespace: 'public',
}
);
await getEditView(editSchemaObj, initDataProc);
});
it('proiswindow visible', async ()=>{
let editSchemaObj = new FunctionSchema(
() => new MockSchema(),
() => new MockSchema(),
{
role: [],
schema: [],
getLanguage: [],
getTypes: [],
getSupportFunctions: [],
},
{
node_info: {
connected: true,
user_id: 1,
username: 'postgres',
version: 130005,
server: {
host: '127.0.0.1',
port: 5432,
server_type: 'postgres',
user: {
id: 10,
name: 'postgres',
is_superuser: true,
can_create_role: true,
can_create_db: true,
},
},
},
},
{
type: 'procedure',
},
{
funcowner: 'postgres',
pronamespace: 'public',
}
);
let initData = ()=>Promise.resolve({
sysproc: true,
type: 'procedure',
});
await getEditView(editSchemaObj, initData);
});
it('proparallel disabled', async ()=>{
let editSchemaObj = new FunctionSchema(
() => new MockSchema(),
() => new MockSchema(),
{
role: [],
schema: [],
getLanguage: [],
getTypes: [],
getSupportFunctions: [],
},
{
node_info: {
catalog: {},
connected: true,
user_id: 1,
username: 'postgres',
version: 130005,
server: {
host: '127.0.0.1',
port: 5432,
server_type: 'ppas',
user: {
id: 10,
name: 'postgres',
is_superuser: true,
can_create_role: true,
can_create_db: true,
},
},
},
},
{
type: 'function',
},
{
funcowner: 'postgres',
lanname: 'edbspl',
}
);
await getEditView(editSchemaObj, initDataProc);
});
it('probin visible', ()=>{
let editable = _.find(schemaObj.fields, (f)=>f.id=='probin').visible;
let status = editable({lanname: 'c'});
expect(status).toBe(true);
});
it('prosrc_c visible', ()=>{
let visibleData = _.find(schemaObj.fields, (f)=>f.id=='prosrc_c').visible;
let status = visibleData({lanname: 'c'});
expect(status).toBe(true);
});
it('prosrc visible', ()=>{
let visibleData = _.find(schemaObj.fields, (f)=>f.id=='prosrc').visible;
let status = visibleData({lanname: 'c'});
expect(status).toBe(false);
});
it('prorows readonly', ()=>{
let readOnly = _.find(schemaObj.fields, (f)=>f.id=='prorows').readonly;
let status = readOnly({proretset: true});
expect(status).toBe(false);
});
it('prorettypename validate', () => {
let state = {lanname: 'c', prorettypename: null};
let setError = jest.fn();
schemaObj.validate(state, setError);
expect(setError).toHaveBeenCalledWith('prorettypename', 'Return type cannot be empty.');
});
it('probin validate', () => {
let state = { lanname: 'c', prorettypename: 'char' };
let setError = jest.fn();
schemaObj.validate(state, setError);
expect(setError).toHaveBeenCalledWith('probin', 'Object File cannot be empty.');
});
it('probin validate', () => {
let state = { lanname: 'c', probin: 'test1', prorettypename: 'char'};
let setError = jest.fn();
schemaObj.validate(state, setError);
expect(setError).toHaveBeenCalledWith('probin', null);
});
it('prosrc_c validate', () => {
let state = { lanname: 'c', probin : '$libdir/', prorettypename: 'char'};
let setError = jest.fn();
schemaObj.validate(state, setError);
expect(setError).toHaveBeenCalledWith('prosrc_c', 'Link Symbol cannot be empty.');
});
it('prosrc_c validate', () => {
let state = { lanname: 'c', probin : '$libdir/', prosrc_c: 'test1', prorettypename: 'char'};
let setError = jest.fn();
schemaObj.validate(state, setError);
expect(setError).toHaveBeenCalledWith('prosrc_c', null);
});
it('validate', ()=>{
let state = {prorettypename: 'char'};
let setError = jest.fn();
state.prosrc = null;
schemaObj.validate(state, setError);
expect(setError).toHaveBeenCalledWith('prosrc', 'Code cannot be empty.');
state.prosrc = 'SELECT 1';
schemaObj.validate(state, setError);
expect(setError).toHaveBeenCalledWith('prosrc', null);
});
});