caja | Caja , the file manager for the MATE desktop

Remove "dataSrc": "" - you should not need to use the dataSrc option at all, because it looks as if your JSON row data is already in a top-level named array: { ... "data": [...] ... }.

By default, the name used by DataTables for the row iteration entry point is data. So, not using dataSrc at all is the same as using "dataSrc": "data".

If you use "dataSrc": "", that is telling DataTables that your row array is in a JSON structure like this - an array of arrays:

You only need to set the height of cont1 like this:

I LEAVE YOU THE CODE THAT ANSWERS MY QUESTION, I HOPE IT WILL BE VERY USEFUL

Usually, what I like to do when collecting data through webscraping is to build either :

• A list of dictionaries (which contains metadata) (option 1)
• Lists of metadata in a single dictionary with corresponding column names (data, title, price, etc.) (option 2)

(What I call "metadata" is all the pieces of information that describes a single item : in your case, that would be : the item price, the extraction date, the reviews on a specific item, and so on.)

When scraping is done, I build the DataFrame only as a final step.

As a final note, I didn't want to mess with your original script too much, but I think you should consider two things :

• Build a function to wrap your scraping steps (or maybe even a class so you can add a single function that handles all the similar things you're doing : collecting metadata on a product)
• You should probably replace "Sin Marc", "Sin Reviews" with np.nan, it will make your data processing and analysis easier

In the modification I did in your script, I choose option 2. I'm not sure about that, but I would guess that option 2 is more efficient than option 1. However, I find it useful, sometimes, when you handle more complex data to build a dictionary first and then, happen the dictionary corresponding to a single item into a list of dictionaries (that would be option 1) : it can make it easier to track each item at a time.

HTML does not support nested forms, so the browser turns them into one. Which is why your button is outside the form. Remove the nested form and everything will work.

In Javascript, single/double quoted strings are always single line(without line continuations). To fix it, use a multiline string(aka template strings) by using backticks instead:

I rearranged the top part of the code, but once you get the final dataframe you can write that to csv as you were. Also, note I changed a couple list comprehensions to check for errors that I was getting. Also, url_list needs commas.

Mutations shouldn't call other mutations (actions can call multiple mutations) and you shouldn't be interested in return values from mutations/actions.

If you were using a bundler like Vue CLI, it would be best to create a separate module for it (like Utilities.js) and import it into the store and any component.

Since you are using a CDN, you can define estadoFunction above your Vue code. For example:

I see you are trying to work with the Vuex store. And using mutation inside the template syntax.

Not sure if we can call mutation directly via HTML as the way you are doing. In the past when I tried to call a mutation, I would either:

• Create an action which would commit that mutation and call that action wrapped inside a method through Vue, something like this:look for a method printSampleLog() that I defined here