You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Searching for lambda or partial functions in the sidebar doesn't work when including the < or > character, as those interfere with either the search matching or element rendering.
Steps to Reproduce
On the main branch, open demo-project/src/demo_project/pipelines/data_ingestion/pipeline.py
Add a lambda function, like this:
node(
func=lambdax: x,
inputs='x',
outputs='y'
)
Search for <lamb in the sidebar search input
Expected Result
A search result should appear with blue text highlighting the matching search.
Actual Result
Nothing appears.
Note the lambda python functions don't render nicely on the flowchart. That'll be fixed in #851, and once fixed, this is the actual result:
Your Environment
Include as many relevant details as possible about the environment you experienced the bug in:
Web browser system and version: Chrome latest
Operating system and version: Mac Monterey
NodeJS version used (if relevant): 14
Kedro version used (if relevant): 4.5.0
Python version used (if relevant):
Checklist
Include labels so that we can categorise your issue
The text was updated successfully, but these errors were encountered:
Description
Searching for lambda or partial functions in the sidebar doesn't work when including the
<
or>
character, as those interfere with either the search matching or element rendering.Steps to Reproduce
main
branch, opendemo-project/src/demo_project/pipelines/data_ingestion/pipeline.py
<lamb
in the sidebar search inputExpected Result
A search result should appear with blue text highlighting the matching search.
Actual Result
Nothing appears.
Note the lambda python functions don't render nicely on the flowchart. That'll be fixed in #851, and once fixed, this is the actual result:
Your Environment
Include as many relevant details as possible about the environment you experienced the bug in:
Checklist
The text was updated successfully, but these errors were encountered: