Skip to content

add status undecided frontière distinct #509

Description

@boogheta

Some users would like to tackle both usecases of the UNDECIDED status at the same time (both frontier of webentities included but uncrawled, and webentities unsure to include yet). For that usecase, having a 5th SEMI-IN status for the frontier would make sense, but it seems to me like this would require way too many changes in the whole design of both frontend and backend, so I'm more encline to consider this a won'tfix

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions