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
I have just updated SD to version 3.0 (rc1) and everything went perfectly smooth.
One thing I have noticed though is that the new "filePath" attribute has an absolute path:
In our specific case, we're using a custom format that "dumps" the entire structure in a JSON file that it's used in the style guide website, and we can easily remove the "filePath" property from the output, so no big deal per se.
The question I have is: in general, why not use a relative path for this attribute? What is the benefit of having an absolute path for this? (it may cause differences when run on different machines, while the actual tokens remain the same).
The text was updated successfully, but these errors were encountered:
I have just updated SD to version 3.0 (rc1) and everything went perfectly smooth.
One thing I have noticed though is that the new "filePath" attribute has an absolute path:
In our specific case, we're using a custom format that "dumps" the entire structure in a JSON file that it's used in the style guide website, and we can easily remove the "filePath" property from the output, so no big deal per se.
The question I have is: in general, why not use a relative path for this attribute? What is the benefit of having an absolute path for this? (it may cause differences when run on different machines, while the actual tokens remain the same).
The text was updated successfully, but these errors were encountered: