chore(nidaq): improve readbability of nidaq signal definition #71
Open
wakonig_k
wants to merge 1 commits from
chore/nidaq_formatter into feat/various-improvements
pull from: chore/nidaq_formatter
merge into: bec:feat/various-improvements
bec:main
bec:feat/various-improvements
bec:fix/compare_transition_status_refactoring
bec:refactor/ci_from_shared_actions
bec:fix/enums_status_with_list
bec:feat/pilatus
bec:fix_status_set_exception
bec:fix_mono_not_starting
bec:feat/file_structure_nexus
bec:feat/label-group-box
bec:mono-trigger-update
bec:test_new_rebaseing_mono_trigger
bec:Debye_AD
bec:fix-missing-dep
bec:merge-additionaltests-with-test-stage
Dismiss Review
Are you sure you want to dismiss this review?
Labels
Clear labels
issue::not confirmed
issue::not reproducible
issue::reproducible
priority::critical
priority::needed
priority::nice to have
scope::backend
scope::frontend
stage::in development
stage::on hold
stage::pre_release
stage::ready for review
stage::selected for development
stage::weekly backlog
type::bug
type::discussion
type::doc
type::feature
type::improvement
type::test
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Used if an issue has not yet been confirmed by a developer
Used if an issue is not reproducible
Used if a developer was able to reproduce the issue
Should be done as soon as possible
An important update to the code base
Not really needed but a good improvement
An issue regarding the backend services
An issue regarding the user-facing services
This issue is currently being worked on
Something is blocking the development
For issues that have been merged into a pre-release branch and are waiting for their release.
For issues that have been resolved and are ready for review
This issue has been selected for development but has not been scheduled yet
This issue has been selected for development for the next development cycle
It's a bug!
A discussion is wanted/needed
Improvements to the documentation
A new feature
Neither a feature nor a bug but an improvement to the code base
Missing tests or improvements to the test suite
Something is not working
This issue or pull request already exists
New feature
Need some help
Something is wrong
More information is needed
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
acerbo_a (acerbo_a)
appel_c (appel_c)
bec-gitea
celcer_t (celcer_t)
clark_a (clark_a)
debenjak_l (debenjak_l)
divall_e (divall_e)
haghta_s (haghta_s)
hitz_s (hitz_s)
lombosi_c (lombosi_c)
nachtegaal (nachtegaal)
perl_d (perl_d)
tiefenbacher_s (tiefenbacher_s)
usov_i (usov_i)
wakonig_k (wakonig_k)
wang_x1 (wang_x1)
wyzula_j (wyzula_j)
zamofing_t (zamofing_t)
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: bec/debye_bec#71
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "chore/nidaq_formatter"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To improve the readability of the signal definition in the nidaq ophyd device, I propose to disable the formatter. The PR does not change anything else, just formatting
I'm fine with the changes, however they should be made in the feat/various-improvements branch, as we edited that file there already quite a bit.
@hitz_s I can push it to the branch if you want
Sure, just please use the current order of the signals. It is the order in which they are listed in the gui (for example waveform signal selection).
@hitz_s I rebased it on your feature branch and redirected the PR to it.
@hitz_s @clark_a I would suggest that we merge your long-standing feature (feat/various-improvements) branch soon. It is already quite long and has been open for quite some time. If you need help with rebasing or cleanup, just let us know!
Sure, once the digital twin is more or less running.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.