You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any chance both inmemoryBlockOnConsumed and inMemoryBlockOnConsumed could be supported, where inMemoryBlockOnConsumed is mentioned in documentation and also takes precedence? I.e. the old name remains usable for backward compability.
The text was updated successfully, but these errors were encountered:
animir
changed the title
inmemoryBlockOnConsumed vs. inMemoryBlockOnConsumed
Change option name: from inmemoryBlockOnConsumed to inMemoryBlockOnConsumed
Oct 30, 2021
@thernstig Version 2.3.11 supports new inMemoryBlockOnConsumed and inMemoryBlockDuration options as well as just deprecated inmemoryBlockOnConsumed and inmemoryBlockDuration. Deprecated options will be supported until the next v3 major release.
Currently the API uses
inmemoryBlockOnConsumed
as an option, but it would be better ifinMemoryBlockOnConsumed
.It is obviously more correct (camelCase), easier to read and it also does not give spelling error with spelling errors tools such https://github.com/streetsidesoftware/cspell
Any chance both
inmemoryBlockOnConsumed
andinMemoryBlockOnConsumed
could be supported, whereinMemoryBlockOnConsumed
is mentioned in documentation and also takes precedence? I.e. the old name remains usable for backward compability.The text was updated successfully, but these errors were encountered: