feat: deprecate Parsing component and replace them in starter projects #6697
+4,473
−4,286
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
dosubot
bot
added
the
size:XXL
edwinjosechittilappilly
requested review from
lucaseduoli,
ogabrielluiz and
Cristhianzl
CodSpeed Performance ReportMerging #6697 will improve performances by 57.1%Comparing Summary
Benchmarks breakdown
|
lucaseduoli
previously requested changes
Feb 24, 2025
carlosrcoelho
requested review from
lucaseduoli
and removed request for
lucaseduoli
dosubot
bot
added
size:S
|
On testing found a bug in new parser component: data_to_text : test portfolio website generator. |
|
@Cristhianzl @erichare @mendonk Looking forward to your support for review. |
github-actions
bot
added
enhancement
github-actions
bot
added
enhancement
…egacy switch functionality ✨ (similarity.spec.ts): add new test steps to check sidebar options and legacy switch functionality ✨ (loop-component.spec.ts): add new test steps to check sidebar options and legacy switch functionality, as well as zoom out and expand button modal functionality
… Generator.spec.ts, decisionFlow.spec.ts, similarity.spec.ts, generalBugs-shard-9.spec.ts, codeAreaModalComponent.spec.ts, fileUploadComponent.spec.ts, nestedComponent.spec.ts, filterEdge-shard-1.spec.ts, loop-component.spec.ts, generalBugs-shard-12.spec.ts, add-legacy-components.ts): add function to handle legacy components in tests for improved test readability and maintainability
edwinjosechittilappilly
changed the base branch from
main
to
fix/parser_component
github-actions
bot
added
enhancement
edwinjosechittilappilly
force-pushed
the
deprecate-parsing-components
branch
from
50f9690 to
b702139
Compare
github-actions
bot
added
enhancement
|
Do not Merge until. |
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.
This pull request includes changes to mark certain components as legacy and format JSON files for better readability. The most important changes include setting the
legacyattribute toTruefor specific components and formatting theBlog Writer.jsonfile.Marking components as legacy:
src/backend/base/langflow/components/processing/parse_data.py: Addedlegacy = Trueto theParseDataComponentclass.src/backend/base/langflow/components/processing/parse_dataframe.py: Addedlegacy = Trueto theParseDataFrameComponentclass.Formatting JSON files:
src/backend/base/langflow/initial_setup/starter_projects/Blog Writer.json: Reformatted the JSON structure to use arrays foroutput_types,inputTypes,field_order, and other fields for better readability. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]