[FEAT] Rename question in Dataset Configuration#117
Merged
Conversation
…ggestions - Enhance type mapping to handle more Table Schema types (e.g., 'str', 'number', 'datetime', 'any') - Infer metadata types from both schema and sample data for 'any' fields - Use content analysis to detect text annotation fields instead of hardcoded names - Suggest questions based on schema types and data (e.g., label selection for booleans/low-cardinality strings, rating for numeric fields) - Ensure FieldType is correctly serialized as a string in repository methods
Fix MetadataTypes typo, add terms type, and rename adapteType to adaptedType Enhance ImportHistoryDatasetBuilder to handle metadata types correctly Update MetadataRepository to use adaptedType property
Implements a new /import-history API endpoint for importing datasets from import history, and updates the frontend to use it when needed.
…description - Added a header for the metadata section in the DatasetConfigurationForm component. - Changed default metadata fields from "imdb" to "pmid" in both DatasetConfigurationForm and DatasetConfigurationMetadataSelector components. - Updated the metadata description in the translation file to reflect sorting instead of filtering.
…styling for better user experience. - Refactored ImportHistoryList component to streamline search and pagination logic. - Introduced new methods in useImportHistoryListViewModel for better handling of filters and pagination. - Adjusted API response structure for import history to include additional metadata and improved data handling. - Removed unnecessary modal state management from index.vue, delegating it to useHomeViewModel for cleaner code.
- Updated the ImportHistoryDetails component to utilize a new simplified use case for fetching import history details directly. - Removed pagination and filtering logic from the component, transitioning to client-side handling. - Enhanced the useImportHistoryDetailsViewModel to process and summarize import history data more effectively. - Adjusted related types and interfaces to align with the new data structure and response format.
- Updated the ImportHistoryResponse interface to include a structured metadata object with documents and summary. - Refactored the useImportHistoryDetailsViewModel to utilize the new ImportSummary type for better data handling. - Adjusted the calculateSummary method to derive summary information from the updated metadata structure. - Improved the GetImportHistoryDetailsUseCase to align with the new metadata format, ensuring accurate processing of import history details.
…improved functionality and styling - Updated BaseSimpleTable.vue to enhance TypeScript type definitions and streamline SCSS styles for better maintainability. - Adjusted ImportHistoryDataPreview.vue to remove hardcoded pagination size, implementing dynamic pagination based on data length. - Simplified the get-import-history-use-case.ts by utilizing shorthand property names for the limit parameter.
…r experience - Introduced new formatting methods in ImportHistoryDataPreview.vue for boolean, number, and URL display. - Removed the ImportHistoryDetails component and its associated view model, streamlining the import history handling. - Updated ImportHistoryList.vue to simplify the data loading process and removed unnecessary filters. - Enhanced the index.vue to manage import history modals more effectively, improving user interaction. - Adjusted the GetImportHistoryUseCase to limit filters to workspace_id and user_id for cleaner API requests.
- Renamed 'uploaded_by' to 'username' across ImportHistoryList.vue and related use cases for clarity. - Updated ImportHistoryResponse and related schemas to replace 'user_id' with 'username' for a more descriptive response. - Introduced ImportHistoryCreateResponse schema to standardize the response for import history creation. - Adjusted API endpoints to align with the new response structures, enhancing data handling and consistency.
…and functionality - Added Jest testing patterns to the structure documentation for better test organization and clarity. - Updated ImportAnalysisTable.spec.js to include comprehensive mock setups for view models and props. - Refactored ImportAnalysisTable.vue to streamline local state management and introduced a retryAnalysis method for improved functionality. - Enhanced the useImportAnalysisViewModel.ts to include the retryAnalysis function, ensuring proper analysis handling based on props changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.