Skip to content

Templates and scrapers conflict with "list" type fields #1441

@ltning

Description

@ltning

Hi!

I've made some templates and scrapers for my retro hardware collection, and found it useful to have the default template for a collection have all the same fields (plus some) as the fields that may be returned by the scrapers.

For text fields, this works well: I create a new object, all fields are empty. Then I scrape, and it populates the fields with whichever data it finds, leaving those where no data is found empty for me to fill in by hand.

So far, so good.

However, for the field type "List" this does not work: If the template contains such a field, and the scraper contains the same field, also as "List". no data is filled. I've been fighting XPath all day long over this :-)

Renaming either the template or the scraper field solves this, but gives me duplicate fields.

This is probably a relatively simple fix, I hope? :)

Take care, and thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions