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
1. Make "HTML Report" a default view. Rename to "Results".
2. In this "Results" view - names of columns in the table should be more user-friendly: remove "data." prefix and if possible make the rest capitalized and without underscored. So ideally data.markdown will become Markdown and data.number_of_users will become Number of users.
3. Can we add to "Results" a json view like for Overview view?
4. Markdown results should not have CSS or other irrelevant data except text. Content should be cleaned in a similar way as in WCC.
5. List of visible inputs to the user should contain only: Start URLs, Extraction Prompt. The rest of inputs should be hidden. - In json view there shouldn't be apiKey that the user sees. We should add it probably as some kind of secret or env variable. If we keep it like now - it won't be possible for a user to run the actor without entering their API key, but that loses the whole point of having this actor then.
- Same applies to model name.
5. As follow-up from previous point: the input for apiKey and modelName may possibly stay there for a user to fill, but just to override our existing variable. It could be good to give this kind of flexibility to users, but let's skip it in the initial version and add only later based on demand.
6. Default and prefilled values for each input should be updated.
data.markdownwill becomeMarkdownanddata.number_of_userswill becomeNumber of users.apiKeythat the user sees. We should add it probably as some kind of secret or env variable. If we keep it like now - it won't be possible for a user to run the actor without entering their API key, but that loses the whole point of having this actor then.apiKeyandmodelNamemay possibly stay there for a user to fill, but just to override our existing variable. It could be good to give this kind of flexibility to users, but let's skip it in the initial version and add only later based on demand.