I'm going to see how far I can get following these guidelines: https://m.mediawiki.org/wiki/Extension:Echo/Creating_a_new_notification_type
Mon, Oct 21
External Identifier property datatypes correspond to string value types, so (basic) support for these types is enabled via: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseMediaInfo/+/542253. Some UI work will be necessary to improve the experience.
Support for String, Quantity, and URL datatypes is introduced here: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseMediaInfo/+/542253. Follow-up patches will introduce support for more exotic datatypes.
Quantity datatype support is introduced in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseMediaInfo/+/542253, but some updated UI designs are needed to improve the user experience.
Support for URL property types is added in this patch: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseMediaInfo/+/542253. But we're going to need to do a little UI work to improve the user experience before this is really ready for production.
Here's a screenshot of the datatypes that we'll be able to start supporting once this patch gets merged.
Sun, Oct 20
Fri, Oct 18
I'm not attending TechConf this year, but the lack of a common, well-supported local development environment has been a huge pain point during my time here.
Thu, Oct 17
Server-side rendering is not a requirement for this particular component, and the queries made to the server are the same regardless of which tab the user starts on. I agree that a hash fragment may be more appropriate here (and more obvious to the user in terms of meaning). A hash fragment representing a given view should probably change as the user goes back and forth between tabs, but that's pretty simple to implement.
Sorry for the confusion, my asset question was related to the UploadWizard task T234960, getting my tickets confused over here.
I can get a patch ready for this pretty quickly, but do we have assets (vector graphics) and copy for this screen now? @PDrouin-WMF any updates here?
Yeah, that's why I assumed it would work the same way here.
There are two ways this feature could be implemented:
This feature seems like it requires a large amount of behind-the-scenes work for the value it delivers to the user: the global "feed" of images may be constantly changing, which means a user's place within the stack of images is not going to remain constant and may need to be re-calculated every time they change tabs (or even in the background as they work, since other users will presumably be using this tool simultaneously). I'd argue that this feature is not essential at all (or if it is included, is something that should be limited to the "personal" feed).
In the interest of hitting our target release date, I think this feature should be considered a non-critical enhancement that can be add in post-launch. Moving to "Backlog" for now.
Tue, Oct 15
Tue, Oct 1
Mon, Sep 30
Sep 19 2019
I think that it may be worth returning to this issue now that we are working on support for other data types.
Sep 16 2019
Everything works as far as I can tell (I don't have a 3-button mouse to test with), but it introduces some changes to design and behavior that we should make sure are desired.
Sep 12 2019
Sep 11 2019
Sep 10 2019
Since this issue has fallen to the wayside for a while, I want to put an updated summary here so we can see everything in a single comment. My goal is to get final clarification on what the desired behavior here is.
Sep 9 2019
Ok cool – if you are still finalizing the design I can always make visual adjustments in a follow-up patch.
Screenshot of the new "single-track" UI with the patch I'm currently working on:
Sep 7 2019
Sep 4 2019
@alaa_wmde I'm not working actively on this at the moment, so I've un-assigned myself.
Sep 3 2019
Aug 27 2019
Left two small questions in code review. I can approve this tomorrow (which will also fix T228912).
This should be fixed once the patch for T231225 is merged.
Aug 26 2019
Aug 23 2019
Moving to "verify on production", this is all live and working properly on Beta.
This patch has been merged. Regarding QA needs, we've done extensive testing locally but it would be good to go through the basic UW tasks (both within and outside of campaigns) on Beta just to ensure everything is ok. Then this ticket can probably be closed.
Merged some patches yesterday that should have addressed this. Just went to a random file on Beta commons and added a new value; it's label was properly linked from the moment it was added. Please double-check but I think this is fixed.