This repository was archived by the owner on Aug 29, 2025. It is now read-only.
Do not format values with slash on custom lostgrid properties #288
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
This is not really PR but feature question with code example in form of PR to outline the problem.
I'm using lostgrid framework for defining grids. And some of its properties exactly
lost-columnandlost-rowcan have a slash separated values like so:And when it processed through the stylefmt the value becomes space separated
lost-column: 1 / 3;which is not valid value for lostgrid.I'm not sure if it's really a concern for stylefmt to take care of not standard properties, or what would be the best approach to make it work if there is any.
Thanks.