Tag related to the Projects component in the core of Phorge.
Documentation:
Tag related to the Projects component in the core of Phorge.
Documentation:
last cosmetic change on a title with extra "==="
add missing comma
implement tips, simplify (thanks)
@valerio.bozzolan: Would you like to give this a (hopefully) final review? TIA!
Yeah that makes sense, thanks!
Double slam-sgtm
./bin/celerity/map
I find the current iteration too difficult to read, although that may be partially caused by the mutual language barrier.
Oh, I miss-understood the problem statement. The 4096 limit is on the size of the image that we can resize from...
Maybe since "we live in interesting times" we can increase such limit indeed also, but that logic makes some sense (but terrible user experience, I agree lol)
I also thought that, but I think the current limitation (4096 x 4096) is reasonable and was introduced to avoid to scale huge things and mitigate resource exhaustion in thumb generation.
I'd expect it to just resize the image as needed....
The solution was to take direct children project and call $child->setParentProjectPHID($my_parent_phid).
This was more tricky than expected. Basically we "just" need to call PhabricatorProjectsMembershipIndexEngineExtension method materialize() on the parent.
Finally in my Phorge I can kill these milestones \o/
OK. If you are partially mentioning nonsenses in we.phorge.it itself, you are indeed right.
We might come from different user journeys.
Your users might be aware what the project means, and that the project (and its workboard) is archived, and they do have an initial reason to look at this archived workboard (e.g. default view is not "open tasks" but "all tasks")?
My users clicked an external link to some project tag in something called Phorge, and that project has been archived in the meantime, and that project is set to show the workboard by default, and that is now just empty columns (as the default view of workboards is "open tasks"), and that is confusing and unhelpful.