Mvj 542 intendeduse isactive filter

[henrinie-nc]

No description provided.

[juho-kettunen-nc]

See my question on the UI PR, probably should have been posted here instead: City-of-Helsinki/mvj-ui#541 (comment)

I guess the UI change only touches the intended use select form element, which would make the summary page work as expected. But is it a problem for advanced search?

These commits were made after the daily where the new requirements were presented, so I guess these already take them into account, by removing the IntendedUseManager which removed all inactives.

[henrinie-nc]

See my question on the UI PR, probably should have been posted here instead: City-of-Helsinki/mvj-ui#541 (comment)

I guess the UI change only touches the intended use select form element, which would make the summary page work as expected. But is it a problem for advanced search?

These commits were made after the daily where the new requirements were presented, so I guess these already take them into account, by removing the IntendedUseManager which removed all inactives.

API will (now) not do any filter unless the query parameter is provided, so on that end nothing should change. Admin will work completely normally, but it also has the ability to use is_active for filtering intended uses.