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

Graceful error handling for selecting a scope type without a specific scope instance #18203

Open
Azmodeszer opened this issue Dec 11, 2024 · 0 comments
Labels
beta Concerns a bug/feature in a beta release status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application

Comments

@Azmodeszer
Copy link
Contributor

Azmodeszer commented Dec 11, 2024

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.2-beta1

Python Version

3.11

Steps to Reproduce

  1. Create a prefix or cluster or etc.
  2. Select a scope type.
  3. Try to save without selecting an instance of that scope type.

(btw, I can't assign the beta tag to an issue myself, right?

Expected Behavior

Some kind of regular UI error telling the user to select an instance.

Observed Behavior

<class 'ValueError'>

'PrefixForm' has no field named 'scope_id'.
@Azmodeszer Azmodeszer added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Dec 11, 2024
@Azmodeszer Azmodeszer changed the title Graceful error handling for selecting a prefix scope type without a specific scope instance Graceful error handling for selecting a scope type without a specific scope instance Dec 11, 2024
@jeremystretch jeremystretch added the beta Concerns a bug/feature in a beta release label Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
beta Concerns a bug/feature in a beta release status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants