User Details
- User Since
- Jan 19 2022, 10:47 AM (123 w, 5 d)
- Availability
- Available
- LDAP User
- Russ Rogovetz
- MediaWiki User
- Unknown
Dec 15 2022
I can't continue to do that task.
Dec 9 2022
@Dreamy_Jazz I can't continue to do that task. Sorry.
Nov 4 2022
The getNativeData was removed from GlobalCssJs. So the task can to close.
Sep 29 2022
Good day @Dreamy_Jazz. Can I take that task?
Aug 19 2022
Aug 3 2022
Jul 28 2022
Jul 21 2022
Jun 30 2022
Jun 13 2022
Jun 2 2022
May 18 2022
May 17 2022
May 11 2022
May 2 2022
Apr 25 2022
Apr 20 2022
Apr 19 2022
Apr 15 2022
Apr 13 2022
Apr 12 2022
Apr 8 2022
Apr 4 2022
Mar 30 2022
Mar 29 2022
Mar 16 2022
Mar 15 2022
Mar 11 2022
Hello team,
I'm working on those sub-tasks to replace Content::getNativeData() to TextContent::getText().
For me is not clear how to replace it in EntityContent as it didn't have any dependency with TextContent.
So we have public method getNativeData in EntityContent that implements from Content, we call this method in getSize(). As we deprecate Content::getNativeData we should remove any usage of this method there.
And as I understand well the propose was to replace it with TextContent::getText().
Could you please provide more details about better way to replace it?
Mar 10 2022
Mar 4 2022
Hello team.
I just checked current ticket, there is no place where ::getNativeData() used. So probably it out of date so we could closed a ticket.
Mar 3 2022
Mar 2 2022
Feb 28 2022
Feb 22 2022
Hello team!
I started researching how api "recentchanges" works and where to add the "rcrelated" parameter.
As a result, I didn't found an implementation for "Special: RelatedChanges / Special: RecentChangesLinked" that should be connected.
Therefore, I wanted to clarify with you a scope of work on this task.
As I understand well I need to add the "rcrelated" parameter, to be supported by API. So in future when "Special: RelatedChanges / Special: RecentChangesLinked" will be implementing they will already have required API?
Looking forward to a reply.
Thank you.
Feb 4 2022
Hello team!
I pick up current ticket as "good first task". During the research I found that the issue already resolved. The method "showViewError" selects the user interface language with "getContext()->getLanguage()" and the error is displayed correctly. So probably we could close the current ticket. Correct me if I miss something?