<@U2ASTKU79> idea of one SDF per "feature" is nobl...
# sdf
s
@mattdahse idea of one SDF per "feature" is noble, except NS is one giant shared database, so the projects are likely to reuse record types and/or code. How do you manage that? A separate SDF project for shared assets?