Skip to content

Issues: A248/DazzleConf

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.

Sign up for GitHub

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

21 Open 21 Closed
21 Open 21 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Long Config Value Locked at Lower Value
#44 opened Feb 17, 2024 by Swedz
3
Map Key Requirement for Serializer (Hocon)
#43 opened Jan 4, 2024 by klaidoshka
Handle invalid config values individually with cleanup callback enhancement New feature or request
#42 opened Aug 30, 2023 by A248 2.0.0
make ConfigManager from documentation part of api enhancement New feature or request
#41 opened Aug 30, 2023 by gepron1x
1
Define a structure for configuration definitions enhancement New feature or request
#40 opened Aug 29, 2023 by A248 2.0.0
Turn all serialization to use the value serializer model enhancement New feature or request
#39 opened Aug 29, 2023 by A248 2.0.0
2
Map method names to configuration keys automatically (deprecate @ConfKey?) enhancement New feature or request feedback wanted Feedback especially wanted on this issue
#38 opened Aug 29, 2023 by A248 2.0.0
Type-safe configuration migration enhancement New feature or request
#37 opened Aug 29, 2023 by A248 2.0.0
Please Read: Requiring default values for 2.0 + related changes feedback wanted Feedback especially wanted on this issue
#36 opened Jul 29, 2023 by A248 2.0.0
Bytecode-powered optional enhancements
#35 opened Jul 15, 2023 by A248 2.0.0
1
Suggestions for a better DazzleConf
#33 opened Feb 8, 2023 by BlueTree242 2.0.0
1
Consider deprecating @ConfSerialisers? feedback wanted Feedback especially wanted on this issue
#32 opened Jan 2, 2022 by gepron1x 1.3.0
1
Entire map of nested sections is reset to default when one section is missing a required key bug Something isn't working
#31 opened Dec 31, 2021 by BlueTree242 2.0.0
4
Feature: Implement nested map deserialization to configuration calls as a native exposed functionality enhancement New feature or request
#30 opened Nov 17, 2021 by auriium2 2.0.0
Optionals let you leave out keys enhancement New feature or request
#28 opened Nov 7, 2021 by auriium2 2.0.0
7
Type-Safe Placeholders/Templating with ValueSerialiser integration enhancement New feature or request feedback wanted Feedback especially wanted on this issue
#27 opened Jul 30, 2021 by gepron1x 2.0.0
4
Consider deprecating dotted paths in @ConfKey feedback wanted Feedback especially wanted on this issue
#24 opened Jun 11, 2021 by A248 1.3.0
Feature: Add some sort of reload helper enhancement New feature or request
#21 opened May 24, 2021 by auriium 2.0.0
2
Option: Allow default methods to be used to provide default values for the configuration enhancement New feature or request
#20 opened Apr 30, 2021 by auriium 2.0.0
TOML Support enhancement New feature or request help wanted Extra attention is needed
#12 opened Jan 11, 2021 by A248 1.3.0
2
More configuration format support enhancement New feature or request feedback wanted Feedback especially wanted on this issue help wanted Extra attention is needed
#2 opened Sep 26, 2020 by A248
1
3
ProTip! Mix and match filters to narrow down what you’re looking for.