Skip to content

History / Settings.NullableShortHand

Revisions

  • Remove the duplicate H1 title from wiki pages and deep-link Settings Reference entries GitHub Wiki already renders the page name as the title, so a leading # heading made it appear twice. Home keeps its heading as it names the project rather than repeating "Home". Settings Reference rows for settings documented on a shared page now link to the relevant section.

    @sjh37 sjh37 committed Sep 10, 2026
  • Complete the per-setting pages, and turn Settings-Reference into the index Twenty more pages, covering the settings that were left. All 118 settings on Settings now have a page, and Settings-Reference.md is a generated A-Z table linking each name to it. Settings that are always set together share a page: the five class modifier settings, the two collection settings, the three connection string settings, the folder settings, the namespace settings, the enum settings, the four MultiContextAllFields callbacks, and the read-only runtime values. The index links every setting name, so the reader never needs to know which page a setting lives on. Filtering gains generated before-and-after output for IncludeViews, and RowVersion-and-TimeStamp-columns gains the generated entity, both checked by the drift test like the rest. The sidebar now points at the index rather than listing pages, and Settings-Callbacks keeps its pipeline overview above links to the individual callback pages.

    @sjh37 sjh37 committed Aug 30, 2026
  • Add pages for the core, namespace, view and relationship settings Nine more, several of them shared pages for settings that only make sense read together: the three provider/template settings, the three connection string settings, the namespace settings, the enum settings, the folder settings, and the two nullability spelling settings. Plus ViewProcessing, AddExtraForeignKeys, UseMappingTables and the timeout pair. ViewProcessing is the one worth reading. A view has no primary key, so the generator falls back to treating every non-nullable column as part of a composite key - which silently makes EF de-duplicate rows that are not duplicates.

    @sjh37 sjh37 committed Aug 30, 2026