v1.1.12

Version 1.1.12

• Fixed bug in string_format parsing when just an integer is specified (default to left justification) ex: f'{str:10}'
• Fixed ValueError messages when incorrect string_format specified
• Tried to clean up confusing documentation which describes string_format
• Protect against accidental changes to enum values
  • Return a tuple instead of list for constants
  • Added read-only properties, and set attributes names with leading underscore (_) as a hint that the value shouldn't be modified
• Added missing GREY aliases in AnsiFormat
• Other minor documentation updates

https://pypi.org/project/ansi-string/1.1.12/

v1.1.11

Version 1.1.11

• Fixed bug where underline enable code was required just before setting underline color RGB in parsing ANSI string; otherwise, the sequence wouldn't have previously been parsed properly
• Removed AnsiFormat.setting and added AnsiFormat.ansi_settings which is now a list of AnsiSetting instead of a single AnsiSetting
• AnsiFormat.rgb() functions now return a list of AnsiSetting
• AnsiString can now recursively parse lists within incoming settings
• Added AnsiFormat.color256() and AnsiFormat.colour256() functions

https://pypi.org/project/ansi-string/1.1.11/

v1.1.10

Version 1.1.10

• Parse format spec using a regular expression instead of the crazy logic of before
• Updated __format_spec name to format_spec in to_str() methods - this may cause a little bit of backwards incompatibility if it was ever called out by name

https://pypi.org/project/ansi-string/1.1.10/

v1.1.9

Version 1.1.9

• Allow the fill character in format string to be colon by looking for expected directives in each split

https://pypi.org/project/ansi-string/1.1.9/

v1.1.8

Version 1.1.8

• Tweaked the meaning of topmost in apply_formatting to also extend to all settings leading up to the start index. This means when topmost=False, it will always be masked by all other settings that exist within the applied range, even if the settings were started previous to the given start.
• Added find_settings() to be able to find where any given settings are applied
• Reduced width of README images so they don't get condensed by github/pypi
   
  https://pypi.org/project/ansi-string/1.1.8/

v1.1.7

Version 1.1.7

• Fixed issue where multiple separate escape sequences weren't being parsed from an incoming ANSI string
• The to_str() method now takes in reset_start and reset_end booleans
• Refactoring and docstring corrections/updates in code
• Documented parse functionality in Usage of README - these are now official features
• Added rainbow example to README
• Cleaned up README to try and reduce confusion

https://pypi.org/project/ansi-string/1.1.7/

v1.1.6

Version 1.1.6

• Renamed project from ansi-string to ansi_string to conform with PEP 625
• Added is_formatting_parsable() and is_formatting_valid() functions

https://pypi.org/project/ansi-string/1.1.6/

v1.1.5

Version 1.1.5

• AnsiSetting.parsable now dynamically determines parsability based on the setting string
  • This means that all incoming settings are parsed to determine if the formatting is optimizable, not just specific types
  • This fixed an issue with strings generated with settings from AnsiFormat.rgb() functions were marked as not optimizable
• Break out ANSI parsing functionality into its own file: ansi_parsing.py (accessible but not yet documented)
• AnsiString.simplify() and AnsiStr.simplify() now throw out AnsiSetting objects that contain invalid characters which would terminate the escape sequence
• Fixed some issues related to function code sequence detection (38, 48, 58)

https://pypi.org/project/ansi-string/1.1.5/

v1.1.4

Version 1.1.4

• Fixed bug which would make an incoming string with ANSI directives not optimizable
• Incoming reset directive in string or int on formatting or construction will be allowed but will cause is_optimizable() to return False
• Added is_optimizable() and simplify() to AnsiStr
• Updated documentation

https://pypi.org/project/ansi-string/1.1.4/

v1.1.3

Version 1.1.3

• Removed the need to keep AnsiStr simplified
• Incoming AnsiSetting will not be optimized
• Relaxed documentation about what setting inputs are not advised now that basic strings and ints are parsed and validated

https://pypi.org/project/ansi-string/1.1.3/