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

feat(monitor condition): Remove the empty default condition creation #5354

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Ionys320
Copy link
Contributor

@Ionys320 Ionys320 commented Nov 18, 2024

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

  • I have read and understand the pull request rules.

Description

The first PR related to monitors conditions were adding an empty condition. This has been removed since an empty condition disallow monitor saving. Please note this merge may be unwanted the default condition were a feature (but maybe unwished after all?).

E2E has been updated to avoid considering we have a default condition (all conditions count has been reduced by 1, etc).

Fixes #5303

Type of change

Please delete any options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • User interface (UI)

Checklist

  • My code follows the style guidelines of this project
  • I ran ESLint and other linters for modified files
  • I have performed a self-review of my own code and tested it
  • I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
  • My changes generates no new warnings
  • My code needed automated testing. I have added them (this is optional task)

@CommanderStorm
Copy link
Collaborator

My concearn in #5048 (comment) was that

Currently, I think a good percentage of people would not find this functionality and would be then somewhat confused..

=> we need to find a better way to add this only for new monitors. Sadly, I have not had the time to debug how to differentiated the 1.0 and 2.0 DNS monitors and if they are different.

@CommanderStorm
Copy link
Collaborator

Likely extending the dns monitor instead to include an "Record Exists" functionality or setting a wildcard as the default would be better.

@Ionys320
Copy link
Contributor Author

Regarding DNS, adding a default condition may be done during the migration from v1 to v2, no?

@CommanderStorm
Copy link
Collaborator

Yes, that is a possibility

@Ionys320
Copy link
Contributor Author

Likely extending the dns monitor instead to include an "Record Exists" functionality or setting a wildcard as the default would be better.

I prefer the default wildcard. Using defaut values allows us to keep the conditions system for future monitors without needing too much work.

@louislam louislam added this to the 2.0.0-beta.1 milestone Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Beta build: DNS monitor auto add a condition
3 participants