You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.
Currently, the ie_ref must be the name in the Edge JSON file. But there are often mistakes being done, using the page slug instead, as it is much eaiser to locate (the slug is part of the URL when looking it up in the Edge status website).
The slug can be generated based on the name (and the logic already exists in the codebase to generate the Edge link btw). So it might be great to support both the name and the slug as the reference for the update process (during the matching, the comparison would be done against the name, and also against a slug generated from the name). What do you think ?
The text was updated successfully, but these errors were encountered:
Currently, the
ie_ref
must be the name in the Edge JSON file. But there are often mistakes being done, using the page slug instead, as it is much eaiser to locate (the slug is part of the URL when looking it up in the Edge status website).See #559 for the latest occurrence of such a fix.
Since I started contributing here, most of my PRs are about fixing such mistakes: https://github.com/mozilla/platform-status/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Astof
The slug can be generated based on the name (and the logic already exists in the codebase to generate the Edge link btw). So it might be great to support both the name and the slug as the reference for the update process (during the matching, the comparison would be done against the name, and also against a slug generated from the name). What do you think ?
The text was updated successfully, but these errors were encountered: