EnAccess / EnAccess/micropowermanager

[Feature Request]: Add `model` Column to Device Model

Open
#1,095 3 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
PHP
Stars
27
Forks
19
Avg merge
1d 18h
Merged PRs (30d)
27

Description

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/EnAccess/micropowermanager/blob/main/CONTRIBUTING.md) for this project, if it exists.
- [x] I agree to follow the [Code of Conduct](https://github.com/EnAccess/micropowermanager/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://github.com/EnAccess/micropowermanager/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

Devices in the core data model lack a dedicated “model” field, so the app, APIs, and reports can’t store or display model information cleanly.

### Proposed Solution

- Add a nullable `model` column to the devices table.

- Update the App\Models\Device entity and any validation rules to surface this field.

- Extend relevant controllers/API resources so clients can read and write the model value.

### Alternatives Considered

N/A

### Additional Information

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.