This may be totally OK for fresh projects. But in my case, where I'm migrating gradually from Tailwind to PandaCSS with ParkUI this style is too aggressive and takes over styling where I'm not expecting it.
There is a similar problem with Preflight, but it can be scoped with a class name. But in this case, I can't scope it with PandaCSS config, so must manually override the preset after it was created with createPreset
Perhaps this global styles config can either respect preflight scoping or it can be overwritten on createPreset function call.
Or, it should not be global in the first place.
Global styles that set border colour are too aggressive: https://github.com/cschroeter/park-ui/blob/53235fbaf69e5f6b8a1bb8d2518a5816475a1f3c/packages/panda/src/global-css.ts#L18.
This may be totally OK for fresh projects. But in my case, where I'm migrating gradually from Tailwind to PandaCSS with ParkUI this style is too aggressive and takes over styling where I'm not expecting it.
There is a similar problem with Preflight, but it can be scoped with a class name. But in this case, I can't scope it with PandaCSS config, so must manually override the preset after it was created with
createPresetPerhaps this global styles config can either respect preflight scoping or it can be overwritten on
createPresetfunction call. Or, it should not be global in the first place.wdyt?