Development ts client v2 #4
Merged
Conversation
This file contains 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
…ule logic e.g. 'environment.users' point to the users who added to this environment: - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation
- Enhanced and refactored the organization class - Added 'addMember' method to add member to an exact organization - Added 'removeMember' method to remove member from an organization - Added 'delete' method to delete an organization based on it's id - Added 'update' to update the organization name - Added a lock on the request to lock the request until we receive a response then do the other request - Updated the config class to initialize a new instance everytime we use it - Updated the readme file and enhanced the example
Mahmoud-Emad
added a commit
that referenced
this pull request
Apr 28, 2024
…kend server with some missing features (#5) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: (#3) - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * Development ts client v2 (#4) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * WIP: organization implementation: - Enhanced and refactored the organization class - Added 'addMember' method to add member to an exact organization - Added 'removeMember' method to remove member from an organization - Added 'delete' method to delete an organization based on it's id - Added 'update' to update the organization name - Added a lock on the request to lock the request until we receive a response then do the other request - Updated the config class to initialize a new instance everytime we use it - Updated the readme file and enhanced the example * Update: Updated the TSClient with some features, and enhanced the backend server with some missing features: - Created the project management class - Created 'create', 'update', 'get', 'getAll', 'delete' methods as helpers - Updated the 'OrganizationProjectsApiView' in the backend server - Created a landing page on the backend server to guide the user with the available routes and display the current version of the system - Updated the docs with the newly added updates
Mahmoud-Emad
added a commit
that referenced
this pull request
Apr 28, 2024
…kend server with some missing features (#5) (#6) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: (#3) - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * Development ts client v2 (#4) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * WIP: organization implementation: - Enhanced and refactored the organization class - Added 'addMember' method to add member to an exact organization - Added 'removeMember' method to remove member from an organization - Added 'delete' method to delete an organization based on it's id - Added 'update' to update the organization name - Added a lock on the request to lock the request until we receive a response then do the other request - Updated the config class to initialize a new instance everytime we use it - Updated the readme file and enhanced the example * Update: Updated the TSClient with some features, and enhanced the backend server with some missing features: - Created the project management class - Created 'create', 'update', 'get', 'getAll', 'delete' methods as helpers - Updated the 'OrganizationProjectsApiView' in the backend server - Created a landing page on the backend server to guide the user with the available routes and display the current version of the system - Updated the docs with the newly added updates
Mahmoud-Emad
added a commit
that referenced
this pull request
May 6, 2024
* Update: Updated the TSClient with some features, and enhanced the backend server with some missing features (#5) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: (#3) - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * Development ts client v2 (#4) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * WIP: organization implementation: - Enhanced and refactored the organization class - Added 'addMember' method to add member to an exact organization - Added 'removeMember' method to remove member from an organization - Added 'delete' method to delete an organization based on it's id - Added 'update' to update the organization name - Added a lock on the request to lock the request until we receive a response then do the other request - Updated the config class to initialize a new instance everytime we use it - Updated the readme file and enhanced the example * Update: Updated the TSClient with some features, and enhanced the backend server with some missing features: - Created the project management class - Created 'create', 'update', 'get', 'getAll', 'delete' methods as helpers - Updated the 'OrganizationProjectsApiView' in the backend server - Created a landing page on the backend server to guide the user with the available routes and display the current version of the system - Updated the docs with the newly added updates * Update: Added some examples to test the workflow. (#7) * Development backend v0.1.0 (#8) * Update: Working on a new version of the backend: - Changed the relations between tables. - Enhanced the say we storing the features - Working on changing the serializers and refactor it * WIP: updated the environment APIs with some enhancements: - Crteated a unique error wrapper to wrap the error when the user send the name of another environemnt on the same project - Created the get environment by id endpoint - Updated the post environment endpoint ### WIP - Working on enabling the user to update/delete an environment * Feat: Implemented the environment update/delete API endpoints. * Enhancements: Implemented the add-user endpoint for adding a user on an environment and added some enhancements: - Created the add-user endpoint - Document all environment serializers and the view of adding a new user - Looped over the user features and return the user feature value instead of the default environment value ### WIP - Updating the 'add-environment-featrue' to push the created feature to users - Updating the 'update-environment-featrue' to reflect the change with users and set the 'featrue_value' with the new value * Feat: Implemented the update and delete env feature. * Update: Enhanced the backend and implemented some endpoints - Implemented a getter endpoint to get user features - Implemented a setter endpoint to set user featrues - Implemented delete endpoint to delete environment feature - Refactored the old environment endpoints * Update: Implemented some endpoints - Implemented user delete feature endpoint - Document the environment views file
Mahmoud-Emad
added a commit
that referenced
this pull request
May 7, 2024
* Update: Updated the TSClient with some features, and enhanced the backend server with some missing features (#5) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: (#3) - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * Development ts client v2 (#4) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * WIP: organization implementation: - Enhanced and refactored the organization class - Added 'addMember' method to add member to an exact organization - Added 'removeMember' method to remove member from an organization - Added 'delete' method to delete an organization based on it's id - Added 'update' to update the organization name - Added a lock on the request to lock the request until we receive a response then do the other request - Updated the config class to initialize a new instance everytime we use it - Updated the readme file and enhanced the example * Update: Updated the TSClient with some features, and enhanced the backend server with some missing features: - Created the project management class - Created 'create', 'update', 'get', 'getAll', 'delete' methods as helpers - Updated the 'OrganizationProjectsApiView' in the backend server - Created a landing page on the backend server to guide the user with the available routes and display the current version of the system - Updated the docs with the newly added updates * Update: Added some examples to test the workflow. (#7) * Development backend v0.1.0 (#8) * Update: Working on a new version of the backend: - Changed the relations between tables. - Enhanced the say we storing the features - Working on changing the serializers and refactor it * WIP: updated the environment APIs with some enhancements: - Crteated a unique error wrapper to wrap the error when the user send the name of another environemnt on the same project - Created the get environment by id endpoint - Updated the post environment endpoint ### WIP - Working on enabling the user to update/delete an environment * Feat: Implemented the environment update/delete API endpoints. * Enhancements: Implemented the add-user endpoint for adding a user on an environment and added some enhancements: - Created the add-user endpoint - Document all environment serializers and the view of adding a new user - Looped over the user features and return the user feature value instead of the default environment value ### WIP - Updating the 'add-environment-featrue' to push the created feature to users - Updating the 'update-environment-featrue' to reflect the change with users and set the 'featrue_value' with the new value * Feat: Implemented the update and delete env feature. * Update: Enhanced the backend and implemented some endpoints - Implemented a getter endpoint to get user features - Implemented a setter endpoint to set user featrues - Implemented delete endpoint to delete environment feature - Refactored the old environment endpoints * Update: Implemented some endpoints - Implemented user delete feature endpoint - Document the environment views file * Development dart client v1.0.7 (#10) * Update: Changed the types of the dart client - Updated the request/response of adding/getting user features - Commented un-needed caller for now - Added missing fileds in the backend - Fixed the README.md with the newly added changes - Fixed the dart example * Fix: Fixed some issues in the example - Removed dead-code - Added print, to print the result that coming from the server * Bump version to v1.0.7 * Bump version to v1.0.8
Mahmoud-Emad
added a commit
that referenced
this pull request
May 20, 2024
* Update: Updated the TSClient with some features, and enhanced the backend server with some missing features (#5) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: (#3) - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * Development ts client v2 (#4) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * WIP: organization implementation: - Enhanced and refactored the organization class - Added 'addMember' method to add member to an exact organization - Added 'removeMember' method to remove member from an organization - Added 'delete' method to delete an organization based on it's id - Added 'update' to update the organization name - Added a lock on the request to lock the request until we receive a response then do the other request - Updated the config class to initialize a new instance everytime we use it - Updated the readme file and enhanced the example * Update: Updated the TSClient with some features, and enhanced the backend server with some missing features: - Created the project management class - Created 'create', 'update', 'get', 'getAll', 'delete' methods as helpers - Updated the 'OrganizationProjectsApiView' in the backend server - Created a landing page on the backend server to guide the user with the available routes and display the current version of the system - Updated the docs with the newly added updates * Update: Added some examples to test the workflow. (#7) * Development backend v0.1.0 (#8) * Update: Working on a new version of the backend: - Changed the relations between tables. - Enhanced the say we storing the features - Working on changing the serializers and refactor it * WIP: updated the environment APIs with some enhancements: - Crteated a unique error wrapper to wrap the error when the user send the name of another environemnt on the same project - Created the get environment by id endpoint - Updated the post environment endpoint ### WIP - Working on enabling the user to update/delete an environment * Feat: Implemented the environment update/delete API endpoints. * Enhancements: Implemented the add-user endpoint for adding a user on an environment and added some enhancements: - Created the add-user endpoint - Document all environment serializers and the view of adding a new user - Looped over the user features and return the user feature value instead of the default environment value ### WIP - Updating the 'add-environment-featrue' to push the created feature to users - Updating the 'update-environment-featrue' to reflect the change with users and set the 'featrue_value' with the new value * Feat: Implemented the update and delete env feature. * Update: Enhanced the backend and implemented some endpoints - Implemented a getter endpoint to get user features - Implemented a setter endpoint to set user featrues - Implemented delete endpoint to delete environment feature - Refactored the old environment endpoints * Update: Implemented some endpoints - Implemented user delete feature endpoint - Document the environment views file * Development dart client v1.0.7 (#10) * Update: Changed the types of the dart client - Updated the request/response of adding/getting user features - Commented un-needed caller for now - Added missing fileds in the backend - Fixed the README.md with the newly added changes - Fixed the dart example * Fix: Fixed some issues in the example - Removed dead-code - Added print, to print the result that coming from the server * Bump version to v1.0.7 * Bump version to v1.0.8 * Development ts client v4 (#12) * Update: Added some examples to test the workflow. * Update: Working on the TS client: - Enhanced the README file with some extra details of the usage - Updated the full example - Created examples folder and moved all examples there - Fixed the getters and setters in the environment user - User can now get/set a feature for an environment user ### WIP - Update the relationship between the user and the environment and the feature - Improve the database models - Sync the updates with the other clients * feat: Sync backend changes with the TS-Client - Introduced a new behavior for easy object access, e.g., `project.createEnvironment()`. - Organized response types into the `response` folder within `types.ts`. - Organized request types into the `request` folder within `types.ts`. - Updated examples to demonstrate real use cases: creating, interacting with, and deleting objects. - Implemented a `logout` method in the `Auth` module to remove tokens from `config.ini`. - Documented client types, functions, and classes. - Fixed various issues in the backend server. - Improved the environments parser. - Replaced `console.error` with a custom error wrapper. - Applied linting to the client codebase. * v1.0.1 * fix: Export the base module to the top layer. * v1.0.2 * chore: Updated the build process. * v1.1.0 * v1.2.0 * v1.2.4 * v1.2.5 * v1.2.6 * v1.2.7 * v1.2.8 * v1.2.9 * v1.3.0 * v1.3.1 * v1.3.2
Mahmoud-Emad
added a commit
that referenced
this pull request
May 20, 2024
* Update: Updated the TSClient with some features, and enhanced the backend server with some missing features (#5) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: (#3) - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * Development ts client v2 (#4) * Update the module structure by renaming all files to point to the module logic e.g. 'environment.users' point to the users who added to this environment: - Renamed the modules - Refactored the place of 'response' to be under the 'types' file - Moved all response classes to be in the 'response' file - Implemented the most of project plan as a place-setting - Implemented the method of organization creation - Implemented the method of member creation * WIP: organization implementation: - Enhanced and refactored the organization class - Added 'addMember' method to add member to an exact organization - Added 'removeMember' method to remove member from an organization - Added 'delete' method to delete an organization based on it's id - Added 'update' to update the organization name - Added a lock on the request to lock the request until we receive a response then do the other request - Updated the config class to initialize a new instance everytime we use it - Updated the readme file and enhanced the example * Update: Updated the TSClient with some features, and enhanced the backend server with some missing features: - Created the project management class - Created 'create', 'update', 'get', 'getAll', 'delete' methods as helpers - Updated the 'OrganizationProjectsApiView' in the backend server - Created a landing page on the backend server to guide the user with the available routes and display the current version of the system - Updated the docs with the newly added updates * Update: Added some examples to test the workflow. (#7) * Development backend v0.1.0 (#8) * Update: Working on a new version of the backend: - Changed the relations between tables. - Enhanced the say we storing the features - Working on changing the serializers and refactor it * WIP: updated the environment APIs with some enhancements: - Crteated a unique error wrapper to wrap the error when the user send the name of another environemnt on the same project - Created the get environment by id endpoint - Updated the post environment endpoint ### WIP - Working on enabling the user to update/delete an environment * Feat: Implemented the environment update/delete API endpoints. * Enhancements: Implemented the add-user endpoint for adding a user on an environment and added some enhancements: - Created the add-user endpoint - Document all environment serializers and the view of adding a new user - Looped over the user features and return the user feature value instead of the default environment value ### WIP - Updating the 'add-environment-featrue' to push the created feature to users - Updating the 'update-environment-featrue' to reflect the change with users and set the 'featrue_value' with the new value * Feat: Implemented the update and delete env feature. * Update: Enhanced the backend and implemented some endpoints - Implemented a getter endpoint to get user features - Implemented a setter endpoint to set user featrues - Implemented delete endpoint to delete environment feature - Refactored the old environment endpoints * Update: Implemented some endpoints - Implemented user delete feature endpoint - Document the environment views file * Development dart client v1.0.7 (#10) * Update: Changed the types of the dart client - Updated the request/response of adding/getting user features - Commented un-needed caller for now - Added missing fileds in the backend - Fixed the README.md with the newly added changes - Fixed the dart example * Fix: Fixed some issues in the example - Removed dead-code - Added print, to print the result that coming from the server * Bump version to v1.0.7 * Bump version to v1.0.8 * Development ts client v4 (#12) * Update: Added some examples to test the workflow. * Update: Working on the TS client: - Enhanced the README file with some extra details of the usage - Updated the full example - Created examples folder and moved all examples there - Fixed the getters and setters in the environment user - User can now get/set a feature for an environment user ### WIP - Update the relationship between the user and the environment and the feature - Improve the database models - Sync the updates with the other clients * feat: Sync backend changes with the TS-Client - Introduced a new behavior for easy object access, e.g., `project.createEnvironment()`. - Organized response types into the `response` folder within `types.ts`. - Organized request types into the `request` folder within `types.ts`. - Updated examples to demonstrate real use cases: creating, interacting with, and deleting objects. - Implemented a `logout` method in the `Auth` module to remove tokens from `config.ini`. - Documented client types, functions, and classes. - Fixed various issues in the backend server. - Improved the environments parser. - Replaced `console.error` with a custom error wrapper. - Applied linting to the client codebase. * v1.0.1 * fix: Export the base module to the top layer. * v1.0.2 * chore: Updated the build process. * v1.1.0 * v1.2.0 * v1.2.4 * v1.2.5 * v1.2.6 * v1.2.7 * v1.2.8 * v1.2.9 * v1.3.0 * v1.3.1 * v1.3.2 * docs: Updated the docs: - Renamed most of the project docs. - Moved the TSClient docker file to the docker folder.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
WIP: organization implementation: