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
In order for an editor to highlight the location of lint errors, we need to report back the line and column. I think we can achieve that using v3 of the yaml library.
We are thinking that this would require passing structured data to the mixins for just the lint command that contains the line data, maybe more. This would need a spike to figure out how to do this isolating Porter from the Node structs, and not requiring mixins to reinvent the wheel over and over, or have to use Go.
Manifest wide will want linting, this isn't just for the mixins.
The text was updated successfully, but these errors were encountered:
In order for an editor to highlight the location of lint errors, we need to report back the line and column. I think we can achieve that using v3 of the yaml library.
See
We are thinking that this would require passing structured data to the mixins for just the lint command that contains the line data, maybe more. This would need a spike to figure out how to do this isolating Porter from the Node structs, and not requiring mixins to reinvent the wheel over and over, or have to use Go.
Manifest wide will want linting, this isn't just for the mixins.
The text was updated successfully, but these errors were encountered: