Settings: actix.mode has no actix behaviour associated
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by reading the configuration structure and the ApplySettings entry point to confirm how actix.mode is parsed and ignored. The issue presents several alternative designs, so first establish which config ownership and behavior maintainers want; done means the chosen behavior is implemented consistently and its configuration effect is documented.
Written by the indexing model from the issue text.
Description
Your issue may already be reported! Please search on the actix-extras issue tracker before creating one.
Expected Behavior
I expect that all of the settings under the "actix" table correspond to some actix behaviour.
Current Behavior
The config field "actix.mode" has no actix behaviour associated with it, and is ignored by ApplySettings.
Possible Solution
IMO having a mode config is very helpful, being a very common concept, so I suggest it is moved into the application part of the config structure, or another config section being created such as "common" for config that actix-settings provides but doesnt have any implemented behaviour.
Another alternative is for actix-settings to use this mode value to provide different defaults for prod vs dev, and document this.
Steps to Reproduce (for bugs)
Context
Your Environment
- Dominant language
- Rust
- Stars
- 892
- Forks
- 225
- Avg merge
- 8h 57m
- Merged PRs (30d)
- 33
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from actix/actix-extras
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
actix/actix-extras#840 ·
Maintainers usually reply within 1 day
-
A-ws C-bug
Difficulty 3/5 1-2 days Newbie friendliness 65/100
actix/actix-extras#816 · 2 reactions ·
Maintainers usually reply within 1 day
-
A-httpauth C-improvement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
actix/actix-extras#587 ·
Maintainers usually reply within 1 day
-
A-session C-feature
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
actix/actix-extras#501 · 3 reactions ·
Maintainers usually reply within 1 day
-
customizable session key generatorMay be free again A pull request for this issue was closed without being merged. OpenA-session C-improvement good first issue
Difficulty 4/5 3-5 days Newbie friendliness 35/100
actix/actix-extras#497 · 6 comments ·
Maintainers usually reply within 1 day
All issues in actix/actix-extras
Similar issues
-
bug CLI exec session
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
compatibility
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/aws-emulator#30 · 1 comment ·
-
tormach-plasma refusal text with no machine reads "no machine is not declared a plasma machine"Openarea:post bug effort:low P2 source:agent
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Higher Interval Candles draws nothing on a seconds chart whose interval does not divide two hoursOpenbug studies
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
userFRM/egui-charts#2727 ·
Maintainers usually reply within 1 day