Skip to content

Conversation

@RadoBoiii
Copy link
Contributor

@RadoBoiii RadoBoiii commented Apr 1, 2025

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Security enhancement
  • Performance improvement
  • Code refactoring (no functional changes)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added tests that prove my fix is effective or that my feature works
  • All tests pass locally and in CI (npm test)
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules
  • I have updated version numbers as needed (if needed)

Security Considerations:

  • My changes do not introduce any new security vulnerabilities
  • I have considered the security implications of my changes

Additional Information:

Any additional information, configuration or data that might be necessary to reproduce the issue or use the feature.

@vercel
Copy link

vercel bot commented Apr 1, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 10, 2025 4:01pm

@vercel
Copy link

vercel bot commented Apr 1, 2025

@RadoBoiii is attempting to deploy a commit to the Sim Studio Team on Vercel.

A member of the Team first needs to authorize it.

@waleedlatif1
Copy link
Collaborator

@RadoBoiii nice. did we test these tools out? Also, the elasticsearch and redis are missing from the tools/index.ts, I'm not sure if that's intentional or not.

Copy link
Collaborator

@waleedlatif1 waleedlatif1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's remove packages/sdk from the root dir. They may have appeared if you ran npm run dev in the root of the repo, which generates a package.json at the root. Also, let's revert the changes we made to gitignore

@RadoBoiii
Copy link
Contributor Author

@RadoBoiii nice. did we test these tools out? Also, the elasticsearch and redis are missing from the tools/index.ts, I'm not sure if that's intentional or not.

I'm yet to implement them, so I haven't added their tool files yet. Are the other tools running as expected? I will do it once I get everything to work. I will remove the packages/sdk folders and revert the gitignore files

 - included index.ts for redis nd elasticsearch.
 - reverted gitignore to original
 - removed packages/sdk from root
@emir-karabeg emir-karabeg changed the title feat - database tools added #152 feat(database): tools added Apr 1, 2025
restored packages/sdk
- tested mysql and postgre sql
RadoBoiii and others added 2 commits April 2, 2025 22:12
updated packages/sdk
waleedlatif1 and others added 27 commits April 10, 2025 11:58
* feat(autofill): autofill api keys for tools once they are set once

* added setting to settings for envvar autofill, removed from agent block since it depends on the model selected

* add in api key autofill for agent blocks based on existing model provider mapping

* add tooltips for general settings

* resolved pr comments

* reorganized files, removed unused imports
* fix(loops): added resolve for string collections and added single block loop

* improvement(loop-input): error validation removed

* improvement(loops): fixed now for source/external blocks; doesn't work for multi-block loop (>2)

* fix(loops): complex looping functions fully work

* improvement: cleaned up debugging logs
 - included index.ts for redis nd elasticsearch.
 - reverted gitignore to original
 - removed packages/sdk from root
restored packages/sdk
- tested mysql and postgre sql
@RadoBoiii
Copy link
Contributor Author

creating a new PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants