added codegen#344
Open
philipjusher wants to merge 18 commits into
Open
Conversation
…figurations - Introduced `UploadedFile` model for handling file uploads with attributes like `cloud_path`, `file_name`, and `file_size`. - Created `ValidationError` model to represent validation errors, including location, message, type, and context. - Added `ValidationErrorContext` model for additional context related to validation errors. - Implemented `VersionVersionGetResponseVersionVersionGet` model for version response handling. - Defined `VoltageUnit`, `VolumeUnit`, and `VolumetricFlowRateUnit` with respective validation functions. - Developed `WheelInDB` and `WheelInput` models for wheel configurations, including attributes for mass, cost, and traction coefficients. - Added `WheelRollingResistanceConfigs` for managing rolling resistance configurations. - Included a marker file for PEP 561 compliance and shared types for properties in `types.py`. - Updated `tox.ini` to include a new environment for regenerating the API client from the OpenAPI specification.
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
… check Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…rver Co-authored-by: Cursor <cursoragent@cursor.com>
…in CI Co-authored-by: Cursor <cursoragent@cursor.com>
…mples - Restore examples 01-03 to v1 API (app.get_http_client) from before the v2 rewrite - Add examples 04-06 as clones of the v2 workflow using get_conceptev_client() against https://dev-conceptev.awsansys3np.onscale.com/api - Switch examples/config.toml from production to dev environment - Update sphinx_gallery_conf: list all six examples as expected_failing_examples since they all require live server credentials not available in CI - Gitignore conceptev_password, examples output files (results.xlsx, etc) Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
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
2 participants
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.
This pull request introduces a new Python client library for the ConceptEV-API, including initial project scaffolding, documentation, and implementations for several API endpoints. The changes establish the foundation for interacting with the API in both synchronous and asynchronous ways, and provide developer guidance for usage and customization.
Project scaffolding and documentation:
README.mdwith usage examples, authentication details, advanced customization options, and instructions for building/publishing the package..gitignoreto exclude Python build artifacts, environment files, IDE settings, and coverage reports.Client library structure:
conceptev_api_client/__init__.py, exposingClientandAuthenticatedClientfor use.API endpoint implementations:
create_architectures_architectures_post.pyto support creating architectures via POST, with both sync and async methods, parameter handling, and response parsing.delete_architecture_architectures_item_id_delete.pyto support deleting architectures by ID, including parameter handling, sync/async methods, and error handling.