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
Today we can deploy globals if we have one resource per global.
There are real cases when package can contain of hundred+ globals which templated name, similar what is used for class packages.
Let's add wildcards for global resources, which will let to include all the files that will start from a specific name, e.g. resource:
will import all the globals which names start from dc., e.g. dc.global1.xml, dc.global2.xml, etc.
The text was updated successfully, but these errors were encountered:
Today we can deploy globals if we have one resource per global.
There are real cases when package can contain of hundred+ globals which templated name, similar what is used for class packages.
Let's add wildcards for global resources, which will let to include all the files that will start from a specific name, e.g. resource:
will import all the globals which names start from dc., e.g. dc.global1.xml, dc.global2.xml, etc.
The text was updated successfully, but these errors were encountered: