We currently list all the test packages, whereas these were designed to only be used during testing. We should respect 'hidden = TRUE' in .info files, and not record these in our package management.

Comments

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented
Status: Active » Needs review

Commit 8d17191 in dev/site-packages fixes this.

anarcat’s picture

anarcat CreditAttribution: anarcat commented

Shouldn't this policy be decided in the frontend (and thefore be more overridable)? Can it be?

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented

I really think we should just respect the 'hidden' flag. Are you suggesting that we should pass such an option down to Provision, or that we should gather everything, and start tracking which packages are hidden, so we can filter them from Views, etc.?

anarcat’s picture

anarcat CreditAttribution: anarcat commented

I was asking whether or not this flag was actually propagated to the frontend, or whether it should be.

If it's not right now, i'm okay with it being blocked in the backend for now.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented

The hidden flag is not currently passed to the front-end.

This currently filters out hidden packages when they're .info files are initially parsed.

So, is this RTBC, then?

anarcat’s picture

anarcat CreditAttribution: anarcat commented

yes, except i haven't tested anything anywhere today. :)

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented
Status: Needs review » Fixed

Merged into hosting and provision from dev/site-packages.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.