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
Idea by Shai Sinai from comments to compiler blogpost. Potential future feature.
Create a possibility to parse certain files specifically e.g. to support excels and not only text. Also possible to use it to support web sources. Current implementation ideas:
create an interface that takes in raw file content and returns container with data
possibility to register instances of these interfaces in connection with e.g. file extension
how to handle complex internal structure universally ? e.g. excel has sheets ? Either transparent path - load( 'DIRECTORY/my_custom_data.xlsx/excel_sheet_name' ), or kind of hash query in JS - load( 'DIRECTORY/my_custom_data.xlsx#some-query-specific-to-plugin?param=12345' )
how to pass mockup loader internal parameters to the plugin. E.g. encoding, amount, date formats ... parameters - there might be too many, they may change in future. Probably a table of name-value strings would be better.
The text was updated successfully, but these errors were encountered:
Idea by Shai Sinai from comments to compiler blogpost. Potential future feature.
Create a possibility to parse certain files specifically e.g. to support excels and not only text. Also possible to use it to support
web sources
. Current implementation ideas:questions:
load( 'DIRECTORY/my_custom_data.xlsx/excel_sheet_name' )
, or kind of hash query in JS -load( 'DIRECTORY/my_custom_data.xlsx#some-query-specific-to-plugin?param=12345' )
The text was updated successfully, but these errors were encountered: