emallson/scorecard - Change 5TB4BZA7OTPT46NXDH357PTFUNIRJJWEHUQRDKGPY6FWFSLZ3G6QC

hotfixes now split weeks correctly. would you believe that it was (mostly) the same TZ issue?

Created by emallson on February 28, 2021

5TB4BZA7OTPT46NXDH357PTFUNIRJJWEHUQRDKGPY6FWFSLZ3G6QC

Dependencies

In channels

main

production

test

Change contents

Replacement in client/src/model.ts at line 2 [4.308562]
B:BD[4.308617] → [5.2452:2481]
```
  26: new Date(2020, 11, 8),
```
[4.308617]
[4.308647]
```
  26: new Date('2020-12-08T17:00:00-00:00'),
```

Replacement in client/src/EncounterOverview.tsx at line 309 [4.310127]

B:BD[6.10559] → [6.10559:10650]

        segs: seg_hotfixes ? [...segs, { logs: current, hotfixes: seg_hotfixes }] : segs,

[6.10559]

[6.10650]

        segs: [...segs, { logs: current, hotfixes: seg_hotfixes }],

Replacement in client/src/EncounterOverview.tsx at line 325 [4.310127]

B:BD[2.717] → [2.717:812]

          <legend className="font-bold ml-1">{(ix === 0) ? `Week ${props.week}` : ''}</legend>

[2.717]

[2.812]

          <legend className="font-bold ml-1">{(ix === 0) ? `Week ${props.week}` : ''}&nbsp;</legend>

Replacement in client/src/EncounterOverview.tsx at line 339 [4.310127]
B:BD[6.11795] → [6.11795:11820]
```
  return <>{overview}</>
```
[6.11795]
[7.2435]
```
  return <div className="flex">{overview}</div>
```

Replacement in client/src/Changelog.tsx at line 6 [8.2744]

B:BD[3.6615] → [3.6615:6898]

    messages: ['Added distribution information for pull count and progression time to each encounter overview, along with (inverted) percentile information. See the <a class="underline" href="/faq#What-percentile-is-best-for-pull-counts-and-progression-times">FAQ</a> for details.']

[3.6615]

[3.6898]

    messages: [
      'Added distribution information for pull count and progression time to each encounter overview, along with (inverted) percentile information. See the <a class="underline" href="/faq#What-percentile-is-best-for-pull-counts-and-progression-times">FAQ</a> for details.',
      'Mid-reset hotfixes are now correctly attached to the first raid night following the hotfix. Note that we only have estimated times for historical hotfixes, so in some cases it may be one day off due to timing.'
    ]