Sorry, but this is not valid. I can't leave this uncommented.
Assume the article is right, then all metrics would be bad. Thus we
can't find any example that contradicts the statement in the article.
If we pick coverage of automated tests as a metric, then _more_ test
coverage would be bad given
I think it was doomed to fail as soon as people argued that an organization
with an ~$80m annual budget had too many "resource constraints" to address
a backlog of bugs in its core product. That happened in the first five or
so replies to the thread!
On Sun, Mar 24, 2019 at 10:05 PM John Erling
Thanks a lot! The gist certainly helped a lot.
I think the key line in your code, and what Alex was referring to, was this
one: this.$content.empty().append( $content );
But I like the idea of formalizing the process into an object. I will
likely take a slightly different approach, in which
It is a strange discussion, especially as it is now about how some
technical debts are not _real_ technical debts. You have some code,
and you change that code, and breakage emerge both now and for future
projects. That creates a technical debt. Some of it has a more
pronounced short time effect
You absolutely can attach a jQuery element into your $content parameter.
That will work, and probably give you what you want.
However, one of the more powerful things about OOUI is its ability to
encapsulate this type of work. In this case, what I would recommend, is
creating your own custom
In the script I am working on,[1] I have a PanelLayout that is defined like
this:
this.previewResult = new OO.ui.PanelLayout({
expanded: true,
padded: true,
framed: true,
$content: ''
});
Later on, I would like to modify the content of
I haven't dealt with OOUI for a couple of years but maybe you could pass a
jQuery object to the $content parameter, store it yourself, then modify
that later?
On Sun, 24 Mar 2019 at 14:14, Huji Lee wrote:
> In the script I am working on,[1] I have a PanelLayout that is defined like
> this:
>
>
