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
{{ message }}
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
[Feature] Introduce more compact style for ExpressionNode strings #4049
This verbose style is great for being able to read the generated expressions but it also causes the expression size to grow faster, which can be problematic for complex animations that reach the 1000 character limit. Being able to read the generated expression is not that useful for consumers of the toolkit since the string is not exposed publicly, the only place I have seen it surface is when the Windows APIs throw an exception because of its length.
Describe the solution
It would be nice if it automatically generated (or at least, we could choose to generate) compact strings that are functionally equivalent but shorter, e.g
Looks like in the recent PR #4014 these identifiers were changed to guids, which are also relatively long but don't refer directly to class names either, so adopting shorter identifiers shouldn't have negative side effects.
with logic that returns unique, sequential, minimal-length ids (e.g. 'a', 'b', ... 'z', 'aa', 'ab' ...)
Describe alternatives you've considered
The current design of the animation API, which exposes public extension methods that take the ExpressionNode but keeps ExpressionNode.ToExpressionString() as an internal method, makes it impossible to manipulate/transform the generated animation strings from outside the toolkit. If ToExpressionString() were to be made public, developers would be able to transform the strings if they want/need to.
Activity
Kyaa-dost commentedon May 27, 2021
@arcadiogarcia Thanks for highlighting your interest in this area. Opening this for further discussion to gain more input from the community,
michael-hawker commentedon Aug 31, 2021
@arcadiogarcia your PR addressed this right, we can close the issue?
arcadiogarcia commentedon Aug 31, 2021
@michael-hawker Sure, closing it!