Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider renaming fail_map to error_map #1446

Open
mre opened this issue Jun 14, 2024 · 3 comments
Open

Consider renaming fail_map to error_map #1446

mre opened this issue Jun 14, 2024 · 3 comments

Comments

@mre
Copy link
Member

mre commented Jun 14, 2024

We no longer use the term failure in our system; we now refer to it as error. Therefore, it makes sense to rename fail_map to error_map for consistency. Similar to #1443, this will introduce a breaking change, but since we haven't reached a stable version yet, I want to address these naming inconsistencies beforehand.

@mre
Copy link
Member Author

mre commented Jun 14, 2024

Related discussion, which could be tackled at the same time: #1013

@thomas-zahner
Copy link
Member

I totally agree with that change 👍

As for #1013 this was actually already implemented in 250f7a8. Although, I think that the text field is a bit verbose, maybe we could reduce to just the HTTP status text.

The current JSON output looks like:

  "success_map": {
    "http://www.example.com/": [
      {
        "url": "https://www.iana.org/domains/example",
        "status": {
          "text": "OK (200 OK)",
          "code": 200
        }
      }
    ]
  },

@mre
Copy link
Member Author

mre commented Jun 24, 2024

Yup, sounds like a good idea!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants