github-starred/flowsint
2
0
Fork 0
mirror of https://github.com/reconurge/flowsint.git synced 2026-05-07 12:26:24 -05:00
Code Issues 264 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #121] Documentation update needed: extract_input_schema deprecated and import path unclear #90

New Issue
Closed
opened 2026-04-11 08:42:20 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-11 08:42:20 -05:00
Owner
Copy Link

Originally created by @gustavorps on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/121

Description:

While following the documentation at https://www.flowsint.io/docs/developers/managing-types#categorizing-your-type. I noticed an issue with the extract_input_schema utility.

The docs reference extract_input_schema, but this function appears to be deprecated and it’s not clear where it should be imported from.

From the source code, the correct import seems to be:

from flowsint_core.utils import extract_input_schema_flow

Suggested updates:

  • Clarify how to import the function in the documentation
  • Rename all references of extract_input_schema to extract_input_schema_flow
  • Optionally note that extract_input_schema is deprecated (if intentional)

This would help avoid confusion for developers following the guide.

Question:
Is there a recommended way to contribute fixes or improvements to the documentation (e.g. repo location, contribution guide, or PR process)? I’d be happy to help update this if guidance is available.

Thanks!

Originally created by @gustavorps on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/reconurge/flowsint/issues/121 **Description:** While following the documentation at [https://www.flowsint.io/docs/developers/managing-types#categorizing-your-type](https://www.flowsint.io/docs/developers/managing-types#categorizing-your-type). I noticed an issue with the `extract_input_schema` utility. The docs reference `extract_input_schema`, but this function appears to be deprecated and it’s not clear where it should be imported from. From the source code, the correct import seems to be: ```python from flowsint_core.utils import extract_input_schema_flow ``` **Suggested updates:** * Clarify how to import the function in the documentation * Rename all references of `extract_input_schema` to `extract_input_schema_flow` * Optionally note that `extract_input_schema` is deprecated (if intentional) This would help avoid confusion for developers following the guide. **Question**: Is there a recommended way to contribute fixes or improvements to the documentation (e.g. repo location, contribution guide, or PR process)? I’d be happy to help update this if guidance is available. Thanks!
GiteaMirror commented 2026-04-11 08:42:22 -05:00
Author
Owner
Copy Link

@dextmorgn commented on GitHub (Feb 10, 2026):

Hello @gustavorps,

You are absolutly right, new changes were included recently and the documentation is now broken. (it's actually broken in many more places).

I'll free some time to update it.

The website containing the doc is not open for now, but it would indeed be a good idea to make it public so the community can help with the documentation.

In the meanwhile, you can take a look at this to see how types are managed now.

Let me know if you have any more questions and thanks for the feedback!

<!-- gh-comment-id:3876198643 --> @dextmorgn commented on GitHub (Feb 10, 2026): Hello @gustavorps, You are absolutly right, new changes were included recently and the documentation is now broken. (it's actually broken in many more places). I'll free some time to update it. The website containing the doc is not open for now, but it would indeed be a good idea to make it public so the community can help with the documentation. In the meanwhile, you can take a look at [this](https://github.com/reconurge/flowsint/blob/main/flowsint-core/src/flowsint_core/core/services/type_registry_service.py) to see how types are managed now. Let me know if you have any more questions and thanks for the feedback!
GiteaMirror commented 2026-04-11 08:42:22 -05:00
Author
Owner
Copy Link

@dextmorgn commented on GitHub (Feb 23, 2026):

Hello @gustavorps,

I've updated the docs ! Let me know if you have any questions or see any issue.

<!-- gh-comment-id:3943634995 --> @dextmorgn commented on GitHub (Feb 23, 2026): Hello @gustavorps, I've updated the docs ! Let me know if you have any questions or see any issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
documentation
enhancement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/flowsint#90
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?