Releases/v2.6.0 #216
Merged
Releases/v2.6.0 #216
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
replaysMike
commented
Jun 27, 2023
replaysMike
commented
- Fixes Inventory pages for part numbers with '/' characters will not load #164 - Inventory pages for part numbers with '/' characters will not load
- Fixes [Bug]: System info page expects ConnectionString #199 - System info page expects ConnectionString
- Fixes [Bug]: Logs passed to journalctl are filed every character in new log entry #206 - Logs passed to journalctl are filed every character in new log entry
- Fixes [Bug]: Pressing Enter in top Search Box Does Not Work #208 - Pressing Enter in top Search Box Does Not Work
- Fixes [Bug]: Cannot edit a part with a # char in the part name #210 - Cannot edit a part with a # char in the part name.
- Fixes [Bug]: New Inventory Currency does not Default to Config #211 - New Inventory Currency does not Default to Config
- Fixes [Feature Request]: Custom Suppliers - Add to Search and Edit Functions #212 - Custom Suppliers - Add to Search and Edit Functions
- Fixes [Bug]: Selecting Part Type UI Behaviour Akward #213 - Selecting Part Type UI Behavior Akward
- Fixes [Bug]: Spaces aren't encoded/decoded correctly in part numbers #214 - Spaces aren't encoded/decoded correctly in part numbers
- Updated Italian translation
- Fixed unix config using the wrong path for storage provider
…r in new log entry journalctl doesn't handle UTF-8 very well, so forcing the console/log output to ASCII fixes the issue.
Updated systemctl template.
…l not load Fixes #214 - Spaces aren't encoded/decoded correctly in part numbers I couldn't find any other source of this problem, a user reported that the part number appears with %20 in the name of the part. This shouldn't be possible through the UI, unless something was double encoded.
Apprently fetch() will remove text after a # when making a GET request with parameters.
Added support for editing currency/language to Settings page. Defaulted currency to configured value, unless provided otherwise from backend api data.
Added custom supplier id to search, added inline edit functionality
This adds a fix for the weird behavior with semantic-ui's dropdowns. It doesn't let you change the selected text programatically, but I found an odd hack to make it work.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.